@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+hagen
+hk
+lbt
+orignal
+postman
+radakayot
+snex
+wodencafe
Arch
Danny
DeltaOreo
EnforcedParalegal
FreefallHeavens
Irc2PGuest12735
Irc2PGuest42284
Irc2PGuest49442
Irc2PGuest56401
Irc2PGuest59134
Onn4l7h
Onn4|7h
SigSegv
SilentWave
Sisyphus
Sleepy
T3s|4_
Teeed
Wired
acetone_
aeiou
anon
ardu
b3t4f4c3__
bak83
cumlord
death
dr4wd3
eyedeekay_bnc
not_bob_afk
onon_
phil
poriori_
profetik1
qend-irc2p
r3med1tz
rapidash
shiver_
solidx66_
thetia
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.