@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+dr|z3d
+hagen
+hk
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+segfault
+snex
+wodencafe
Arch
BubbRubb
Daddy
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest58427
Irc2PGuest92548
Irc2PGuest96694
Irc2PGuest97710
Leopold_
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SlippyJoe
T3s|4_
Teeed
acetone_
ardu
b3t4f4c3___
b4dab00m
bak83_
boonst
cumlord
death
dr4wd3_
eyedeekay_bnc
onon_1
poriori_
profetikla
r3med1tz-
rapidash
shiver_
solidx66
thetia
tr
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
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.