@eyedeekay
&zzz
+R4SAS
+RN
+StormyCloud
+acetone
+dr|z3d
+hagen
+hk
+orignal
+postman
+radakayot
+snex
+wodencafe
Arch
Danny
DeltaOreo
FreefallHeavens_
Irc2PGuest12735
Irc2PGuest26660
Irc2PGuest39892
Irc2PGuest59134
Irc2PGuest88571
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SpoofIdentify
T3s|4_
Teeed
aeiou
ardu
b3t4f4c3__
carried6590
cumlord
death
dr4wd3_
eyedeekay_bnc
not_bob_afk
plap
poriori_
profetikla
qend-irc2p
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
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