IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2024/05/29
dr|z3d what about 2.6.1 routers? not bothered about those, zzz?
dr|z3d sorry, 2.5.1/2
dr|z3d also, huge kudos for the fix. you're earning your chocolate stars :)
orignal interesting that we have around 900 ffs everywhere
zzz yeah, not sure if we have more fake ones or you have less real ones
zzz dr|z3d, I was offering a general assessment of network conditions, including all ongoing attacks, which do bother me ))
orignal we check real IP addresses vs. published
orignal and if doesn't match we drop such FF
zzz but we do that too, for all routers, not just ff
zzz currently banning only 3 routers for that
dr|z3d I guess I was asking in a roundabout way why you're not explicitly blocking irregular router versions, zzz.
dr|z3d Also, not much consolation, but it appears that Tor's under attack. Either that or the network's gone to shit.
dr|z3d not that you'd know if you asked - status.torproject.org/affected/tor-check
dr|z3d oh, hang on, that's for the check.tp website, let's see if they're saying anything different.. no - status.torproject.org
zzz dr|z3d, indeed, the latest variant appeared just before our 2.5.2 release; at the time, I decided to leave things kindof in a Nash equilibrium, I still feel that was the right call
dr|z3d sure, at least you get a handle on how large the possible attack surface is I guess, assuming the irregular versions are part of an attack.
zzz working thru some complex i2psnark bugs I introduced in 2.5.0; short post on zzz.i2p w/ symptoms and workarounds, will probably be a few days to straighten out
zzz making good progress but testing will take a while