IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2022/06/19
@eyedeekay
&zzz
+R4SAS
+RN
+StormyCloud
+dr|z3d
+hagen
+hk
+orignal
+postman
+snex
+wodencafe
Arch
Danny
DeltaOreo
FreeB
FreefallHeavens_
Irc2PGuest12735
Irc2PGuest465
Irc2PGuest55367
Irc2PGuest59134
Irc2PGuest90168
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
acetone_
aeiou
ardu
b3t4f4c3__
boonst
carried6590
cumlord
death
dr4wd3_
enoxa
eyedeekay_bnc
not_bob_afk
poriori
profetikla
qend-irc2p
r3medi7z
radakayot_
rapidash
shiver_
solidx66
u5657
uop23ip
w8rabbit
weko_
x74a6
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.