@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
Birdy
Danny
FreefallHeavens
Irc2PGuest19087
Irc2PGuest20240
Irc2PGuest57061
Irc2PGuest77260
Irc2PGuest78958
Irc2PGuest82447
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Stormycloud_
T3s|4_
Teeed
aargh2
ac9f
acetone_
anontor
b3t4f4c3___
dr4wd3_
duanin2
duck
gellegery
leopold
makoto
n1_
nilbog
not_bob_afk2
nyaa2pguy
onon_
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
user1
vivid_reader56
w8rabbit
wodencafe2
x74a6
zelgomer
zyx
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