@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+ReturningNovice
+StormyCloud
+T3s|4
+acetone
+cims
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+psychopuck
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
dr|z3d_
duanin2
i2potus
ice_juice
justaperson
luvme
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
orignal
will do this too
orignal
for 1 do you use 3 or 2?
zzz
I fallback to 3 if he advertises both 4 and 3
zzz
and if it's my MTU that is low, I advertise "3" instead of "4,3"
orignal
interesting idea
orignal
let me do it too
zzz
shouldn't happen very often but I need to fix the rest of it
FreefallHeavens
(link directly to mentioned issue) github.com/s-b-repo/i2p-zero-exploits-2026-15-03?tab=readme-ov-file#2-critical-cve-2026-i2p-02-de-anonymization-via-trailing-dot-bypass is this real and how should I edit the i2pProxy.pac file to fix it?
orignal
zzz I have amother question
orignal
say I send SessionRequest with version 4
orignal
but Bob can't honor it and SessionCreated comes with 2
orignal
do we handle such scenario?
zzz
if bob doesn't support he won't be able to decrypt the request, he should catch it earlier with a version check in the header
zzz
bob can send a retry-with-termination, code 20 (VERSION)
orignal
Bob received a packet but declared Alice's MTU is too small
orignal
hence it can decrypt
orignal
but not supposed to send SessionCreated because it doesn't fit Alice's MTU
zzz
well, Alice shouldn't have sent it, but bob can still send retry-with-termination
orignal
fine. so Bob send termination if doesn't fit