@eyedeekay
&zzz
+FreefallHeavens_
+R4SAS
+RN_
+Romster
+StormyCloud
+cims
+eche|off
+hagen
+mesh
+nilbog
+nyaa2pguy
+orignal
+postman
+red
+snex
Arch
Danny
Irc2PGuest28384
Irc2PGuest92627
NiceBoat_
OfficialCIA_
Onn4l7h
Onn4|7h
Over1
SilentWave
Sleepy
Watson
Wikk__
Zapek
aargh4
ac9f
acetone_
ahiru
anontor
calamares
dr4wd3
duanin2
eyedeekay_
eyedeekay_bnc
leopold
mahlay
makoto
marek
mareki2p_
n2
newbie|2
not_bob_afk2
poriori
profetikla
qend-irc2p_
r00tobo
rapidash
test3847473
thetia
uop23ip
utp
vivid_reader56
wodencafe2
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