@RN_
@StormyCloud
@eyedeekay
@postman
@zzz
%snex
+FreefallHeavens_
+Onn4l7h
+Onn4|7h
+altec_lansing
+nyaa2pguy
+poriori
+profetikla
+r00tobo_BNC
Arch
Danny
Irc2PGuest28384
Irc2PGuest78874
Irc2PGuest94591
Liorar
NiceBoat_
OfficialCIA_
Over1
RTP_
SilentWave
T3s|4
U1F642
Watson
Wikk__
acetone_
ahiru
anontor
cims
eyedeekay_
floatyfloatilla
leopold_
mahlay
makoto
mareki2p_
mesh
n2
nilbog
not_bob_afk2
orignal
pory
qend-irc2p_
r00tobo[2]
red
sektorchef
thetia
uop23ip
utp
vivid_reader56
nyaa2pguy
just checking, is i2cp.leaseSetEncType=6,4 / "MLKEM768-X25519 + ECIES-X25519" still "just as weak as ECIES-X25519" but the purpose provides support for routers without PQ?
nyaa2pguy
so if I were building an app using sam i2cp.leaseSetEncType=6 or i2cp.leaseSetEncType=7 would be "better security"?
zzz
6 is hybrid so it is stronger than 4
zzz
so 6,4 means eiteher 6 or 4
nyaa2pguy
got it
nyaa2pguy
thanks
nyaa2pguy
is there any known big performance tradeoff using 6 vs 7
nyaa2pguy
oh dang a quick search makes it seem like 50% slower crypto operations or something
dr|z3d
7 should be considered experimental and not widely supported. 6 is default.
T3s|4
nyaa2pguy: Perhaps you'll find reading and understanding the standard: Module-Lattice-Based Key-Encapsulation Mechanism Standard (FIPS 203) - nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.203.pdf and Recommendations for Key-Encapsulation Mechanisms - nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-227.pdf both instructive :)
T3s|4
As 203 states: This standard specifies three parameter sets for ML-KEM. In order of increasing security strength
T3s|4
and decreasing performance, these are ML-KEM-512, ML-KEM-768, and ML-KEM-1024.
T3s|4
nyaa2pguy: fwiw - on my IRC tunnel: using MLKEM768+ECIES on postman's irc server (only) works well for me :)
nyaa2pguy
thank you! I will read those
T3s|4
nyaa2pguy: np, perhaps a bit dry at times, but fine examples of focused explanatory writing by some very bright folks :D