@eyedeekay
&zzz
+Irc2PGuest80463
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+dr|z3d
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb1
Chrono
Danny
DeltaOreo
FreeB
FreefallHeavens
HAON
HowardPlayzOfAdmin
Irc2PGuest27560
Irc2PGuest32123
Irc2PGuest61213
Irc2PGuest62565
Irc2PGuest64434
Irc2PGuest71617
Onn4l7h
Over
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3___
bak83
cumlord
dr4wd3
duanin2
duck
eyedeekay_bnc
makoto
nilbog-
nnm--
ohThuku1
poriori_
pory
profetikla
r00tobo_BNC
rapidash
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