@eyedeekay
&eche|on
&zzz
+RN
+RN_
+StormyCloud
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+weko
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest4688
Irc2PGuest60273
Irc2PGuest60468
Irc2PGuest62240
Irc2PGuest84249
Onn4l7h
Sleepy
SlippyJoe
T3s|4_
Teeed
aargh2
ac9f
acetone_
b3t4f4c3___
bak83
dr4wd3
duanin2
eyedeekay_bnc
idk_afk
leopold
makoto
nilbog
not_bob_afk
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66_
u5657
uop23ip
vivid_reader56
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