@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+hk
+lbt
+mareki2p
+orignal
+postman
+segfault
+snex
+weko
+wodencafe
Arch
Danny
DeltaOreo
EnforcedParalegal
FreeB
FreefallHeavens
Irc2PGuest12735
Irc2PGuest137180
Irc2PGuest28373
Irc2PGuest30483
Irc2PGuest59134
Irc2PGuest64178
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
Teeed
acetone_
aeiou
ardu
b3t4f4c3___
bak83_
cumlord
death
dr4wd3
eyedeekay_bnc
hagen_
not_bob_afk
phil
poriori
profetik1
qend-irc2p
radakayot_
rapidash
shiver_
solidx66_
thetia
u5657
uop23ip
w8rabbit
x74a6
orignal
zzz, looks like zzz.i2p doesn't like type 12
orignal
or maybe my issue
zzz
orignal, I have an error in the logs, probably my issue, will work on it early this week, thanks for testing
orignal
fine
orignal
let me run local tests
orignal
just finished stuff today
zzz
oh wait, it is your problem ))))))
zzz
you set enc type in key cert to 0, not 255
orignal
at least your keys are fine
orignal
thanks. will fix
orignal
forgot about it
orignal
got it now
orignal
seems working
zzz
super
zzz
I don't allow ElG enctype + PQ sigtype
orignal
huh? isn't it 4?
orignal
I connect as 4
zzz
I mean in the key cert itself
zzz
where it's always been 0 until now
zzz
for destinations
orignal
it's not about this it's becauce crypto key is occupied
zzz
right, but I just have a quick sanity check to prevent 0 enctype + PQ sigtype in destination key certs, that's the error you hit
zzz
actually for router identity key certs also, the proposal says that combination is not allowed
zzz
255 is required
zzz
happy to hear it worked, well done ))
orignal
great
orignal
now it's time to implement my server side with PQ
orignal
but as I said I want to change signature verification first in streaming
orignal
e.g. just ignore it
orignal
I'm wondering what will be LS size with ML-DSA public key, signature and ML-KEM crypto key
zzz
there's a table in the proposal with the size increases listed
orignal
nevermind crypto is 32 bytes