@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+cumlord
+dr|z3d
+eche|off
+hagen
+not_bob_afk
+orignal
+postman
+qend-irc2p
+snex
Arch
Birdy
BubbRubb
Chrono
Daddy_
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest10330
Irc2PGuest2981
Irc2PGuest46844
Irc2PGuest74154
Irc2PGuest88641
Irc2PGuest92550
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
T3s|4_
Teeed
aargh2
ac9f
acetone_
anontor
b3t4f4c3__
bak83
dr4wd3
duanin2
duck
eyedeekay_bnc
makoto
mareki2p_
nilbog
poriori
profetikla
qwert
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wodencafe2
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