@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BravoOreo
BubbRubb1
Chrono
Danny
FreeB
FreefallHeavens
Irc2PGuest13075
Irc2PGuest16460
Irc2PGuest43180
Irc2PGuest62377
Irc2PGuest81471
Onn4l7h
Onn4|7h
Over
Rogueone
Sisyphus
Sleepy
T3s|4_
Teeed
aargh
aisle
ardu
b3t4f4c3__
cumlord
death
dr4wd3_
duanin2
eyedeekay_bnc
makoto
nilbog-
not_bob_afk
ohThuku1_
poriori
pory
profetikla
r00tobo_BNC
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