@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN
+T3s|4
+acetone
+cims
+dr|z3d
+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
StormyCloud
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
anontor
calamares
dr4wd3
duanin2
i2potus
ice_juice
justaperson
luvme3
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
sahil
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
dr|z3d
either way, if you can't send a response within ~3m, you're probably worth avoiding.
zzz
profiles should do that already
orignal
major is acetone's
jpk68
I have been able to make some pretty decent progress with my SAM implementation in the past few days
jpk68
Was just wondering if anyone might be willing to give some feedback on chosen parameters and such :)
orignal
cmd.append("i2cp.leaseSetEncType=4 inbound.quantity=2 outbound.quantity=2\n");
orignal
you want to set 6,4
jpk68
So that's ECIES_MLKEM768_X25519_AEAD, and it falls back to ECIES_X25519_AEAD?
jpk68
Is this supported in both routers right now?
dr|z3d
6,4 is default these days.
orignal
in i2pd if 6 is not supported by router it will be ignored
dr|z3d
mlkem768 with ecies as fallback.
dr|z3d
older routers are exluded, as orignal's saying. if the router doesn't suport PQ crypto, it won't be able to talk to a 6,4 router.
dr|z3d
(which is probably fine)
jpk68
Ah, thanks. Looks like the SAM docs might be a bit outdated then :D
orignal
wrong
orignal
it 6,4 is not supported it will be considered as 4
jpk68
dr|z3d: Yeah, and by the time this is actually merged into Monero, most people probably won't be using really outdated routers. But I wouldn't know :)
orignal
and it is able to talk to a 6,4 router with 4
jpk68
orignal: Docs say "Clients should set either i2cp.leaseSetEncType=4 (for ECIES-X25519 only) or i2cp.leaseSetEncType=4,0"
orignal
where?
orignal
not ours
jpk68
Under "signature and encryption types"
orignal
zzz should fix it
jpk68
Yes, I wasn't referring to that one ;)
orignal
nobody should use 0 now
orignal
on server side
jpk68
Just curious, is there any reason 768 is the default for ML_KEM?
orignal
1024 is too long
jpk68
Alright, thank you
orignal
I think becuase everybody else uses 768
orignal
I also think to support all ML-KEM types at the time using same x25519 key
dr|z3d
too much overhead, in other words.
orignal
for clent tunnels
dr|z3d
768 was determined to be "good enough".
orignal
yes
orignal
it's everywhere by default
zzz
orignal, I believe I'm set up with logging on ~Akx to look for dropped tunnel builds