IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2026/04/30
&zzz
+FreefallHeavens
+R4SAS
+RN
+StormyCloud
+acetone
+cims
+dr|z3d
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
T3s|4
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
duanin2
i2potus
ice_juice
justaperson
luvme3
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
RN anonymousmaybe, idk is spelled eyedeekay
orignal wrong it's spelled as "ee-de-ka"
eyedeekay major is down and I missed anonymousmaybe's message
RN they were just asking if you were around
RN wait, major is down? I thought i2pd never had disconnects.
RN *** chuckles ***
dr|z3d so, interesting. I figured a 3m grace period for failed searches would be sufficient to differentiate between bogus replies and late ones, but apparently not. or the responses are truly fake.
dr|z3d the question is, if a peer is repeatedly taking over 3m to respond to a query, is it hostile, broken, or is there some other factor I'm missing?
zzz dunno, this is your side quest
zzz see email for a new batch of 70 more "vulnerabilities"
dr|z3d 70 more! joy! thanks.
zzz and also updated spreadsheet on the first 30
zzz all help appreciated
dr|z3d they're removing code from the linux kernel expressly so they don't have to deal with the deluge of ai-generated reports.
dr|z3d roger that.
dr|z3d ok, I'm looking at peers sending "unsolicited" replies, the list is interesting.
dr|z3d this is after we've afforded them a 3m grace window on top of the timeout.
dr|z3d every single peer that's arrived in my ban list has a hash that starts with "C", or did, until a new one appeared just now. So 16/17.
dr|z3d that's not statistically likely, that looks like some sort of coordinated attack.
zzz more likely to be near you keyspace-wise, check the close/neighbors reports on the sybil tab
dr|z3d nothing obvious there, but ok.
zzz also double check that you've actually found all the spots where lookups get sent from, if you missed any you'll be on a goose chase
dr|z3d now tracking the number of unique routers in the grace period cache, and number of routers that time out.
dr|z3d maybe this is of zero consequence, dunno.