@eyedeekay
&zzz
+R4SAS
+RN_
+Stormycloud
+T3s|4
+acetone
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Daddy_
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest13210
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest32330
Irc2PGuest5369
Irc2PGuest74254
Irc2PGuest78101
Irc2PGuest79208
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
SlippyJoe
T3s|4__
Teeed
aargh2
ac9f_
anontor
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gellegery
makoto
n1
nilbog
noidea_
onon_
poriori_
profetikla
r00tobo
rapidash
shiver_
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
wodencafe2
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.