~dr|z3d
@RN
@StormyCloud
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%ardu
%cumlord
%snex
+FreefallHeavens
+HowardPlayzOfAdmin
+bak83
+hk
+mareki2p
+onon_
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
+wew
+woodwose
Arch
BubbRubb
Danny
DeltaOreo
FreeB
FreeRider
Irc2PGuest18287
Irc2PGuest38625
Meow
Onn4l7h
Onn4|7h
Xeha
anontor
f00b4r
maylay
not_bob_afk
pisslord
r00tobo[2]
shiver_1
simprelay
solidx66
u5657
weko_
woodwose`
zer0bitz
dr|z3d
orignal: skank.i2p and git.skank.i2p should now be on 6,4
orignal
no something is wrong
orignal
I see them as 4
orignal
only stats.i2p is 6
orignal
please check
dr|z3d
ok, original, will have a look at the merged code.
cumlord
simp.i2p and the others listed on status.simp.i2p should be 6,4
dr|z3d
you need to make sure they're using 768 variant of the PQ encryption, cumlord
orignal
let's try
cumlord
I think anyway
orignal
remeber 6 is ML-KEM-768
orignal
don't repeat drozd's mistake ))
cumlord
I’m pretty sure that’s the one I used
dr|z3d
orignal will soon all over you like a rash if you didn't :)
orignal
yes, I'm connect to simp.i2p as 6
dr|z3d
zzz: any reason we're only supporting one variant of PQ on the client? wouldn't it be better to support them all? presumably that's 5,6,7?
dr|z3d
one version at a time, I mean.. all versions are supported in tunnel manager, but you have to choose the key size.
dr|z3d
what's your plan for 0, orignal? nuke it as soon as possible?
dr|z3d
I'm half inclined to support everything while we're in a transitional phase, so 0,4,5,6,7.
cumlord
lol 😂
cumlord
Perfect I do not know what I’m doing
dr|z3d
so I think it makes sense on the client side to support all MLKEM variants without having to specify one.
orignal
I'm going to use 6,4,0 by defaukt for proxy
dr|z3d
ELG, ECIES, MLKEM, or everything. Having a ton of different MLKEM options just makes for confusion.
orignal
0 is rarely used anyway
dr|z3d
I think I'm going for 7,6,5,4,0 as the default.
dr|z3d
Sure, we don't set 0 on the server, but on the http client it's default for backward compatibility, just in case.
dr|z3d
server side, sure, pick a MLKEM key size, but on the client, just support everything.
dr|z3d
alternatively, if 768 is what we're likely to use, why not remove 512 and 1024?
orignal
ask zzz
dr|z3d
sure, I'm just thinking out loud, zzz will get back to us.
dr|z3d
for now, because there's extra logic required to support multiple possible MLKEM sizes, I think I'll just hide 512 and 1024 in the UI.
cumlord
makes sense, I should be able to just add that to tunnel config for SAM, will older routers just ignore it?