@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+orignal
+postman
+segfault
+snex
+weko
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest59134
Irc2PGuest59461
Irc2PGuest77557
Irc2PGuest85010
Leopold
Onn4l7h
Onn4|7h
Sisyphus_
Sleepy
T3s|4_
ardu
b3t4f4c3__
bak83
boonst
cumlord
dr4wd3_
duck
eyedeekay_bnc
meowking
not_bob_afk
phil
phobos_
pisslord
plap
poriori
profetikla
qend-irc2p
rapidash
shiver_
solidx66
u5657
uop23ip
w8rabbit
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
ohh
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.