IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/06/19
+R4SAS
+RN_
+Stormycloud
+T3s|4
+acetone
+mareki2p
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+wodencafe
Irc2PGuest16019
Irc2PGuest35412
NiceBoat
Onn4l7h
Over
Sisyphus
T3s|4_
Teeed
aargh4
ahiru
ananas
b3t4f4c3___
dr|z3d
duanin2
ice_juice
marek
n2_
not_bob_afk2
o3d3
p2pworm
poriori
profetikla
r00tobo
sahil
solidx66
uop23ip
urist_
x74a6
zelgomer
SilicaRice what prevents someone from leaking an encrypted LS?
dr|z3d SilicaRice: nothing.
dr|z3d what prevents someone from leaking a private ssh key?
SilicaRice so a combination of "friendship keys" (revokable per-client destination) with encrypted LS (revokable per-client leaseset) would be the ideal DDoS protection then, on the assumption that all clients are known?
dr|z3d depends on your threat model. "ideal" is a movable feast.
SilicaRice a malicious client could leak the leaseset, at which point you just nuke the destination. all the other clients would still be able to connect normally but any DDoSers wouldn't.