&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
AHON1
Arch
BubbRubb
C341
Daddy
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest34479
Irc2PGuest54725
Irc2PGuest61298
Irc2PGuest82088
Onn4l7h
Onn4|7h
Rogueone
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3__
carried6590
cumlord
death
dr4wd3
duanin2
ohThuku1
phil
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
wew
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