@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+acetone
+cumlord
+eche|off
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Chrono
Daddy_
Dann
DeltaOreo
FreefallHeavens_
Irc2PGuest63779
Irc2PGuest70600
Irc2PGuest73831
Irc2PGuest74352
Irc2PGuest88587
Onn4l7h
Over
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh1
ac9f_
b3t4f4c3__
bak83_
combed_tree328
coolbuddy799
dr4wd3_
dr|z3d
duanin2
duck
leopold
makoto
not_bob_afk
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
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