@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+altonen
+dr|z3d
+hagen
+hk
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest50191
Irc2PGuest59134
Irc2PGuest69335
Irc2PGuest99002
Leopold_
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy_
T3s|4_
T3s|4__
acetone_
ardu
b3t4f4c3__
bak83_
boonst
cumlord
dr4wd3
eyedeekay_bnc
mareki2p_
not_bob_afk
onon_1
orignal
poriori
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
eyedeekay
I was thinking about the oddities in the reseed traffic and I had an idea, not sure if it's viable...
eyedeekay
Could we send a signing key from the router attempting the reseed, along with some signed piece of contemporary shared information like a timestamp, in the HTTP headers with the `get` when the reseed is fetched?
eyedeekay
Allowing the reseed server to verify that the agent they are serving the reseed to is likely to be an I2P router?
zzz
there's the user-agent check for wget already
eyedeekay
Yeah I know, just wondering if this is harder to "fake"
eyedeekay
Not sure it is just wondering
zzz
we've isolated the tm botnet to five /24s, if they're still around in a month we'll probably block them in the release