&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+StormyCloud
+cims
+eche|off
+hagen
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Holmes
Irc2PGuest17692
Irc2PGuest28384
Irc2PGuest37450
OfficialCIA
Onn4l7h
Onn4|7h
Over1
Sleepy
T3s|4_
U1F642
Zapek
aargh4
ac9f
acetone_
ahiru
ananas_
dr4wd3
duanin2
leopold
mahlay
makoto
marek
mareki2p
n2_
not_bob_afk
poriori_
profetikla
r00tobo
rapidash
test3847473
uop23ip
urist_
x74a6
zelgomer
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