@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+acetone
+altonen
+dr|z3d
+eche|off
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
AHOH
Arch
BubbRubb
Daddy_1
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest17402
Irc2PGuest5096
Irc2PGuest89334
Leopold
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
SlippyJoe
T3s|4_
Teeed
ardu
b3t4f4c3___
cumlord
dr4wd3_
eyedeekay_bnc
idontpee
ohThuku1
onon_
poriori
profetikla
r00tobo
rapidash
rascal
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
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