Replies: 3 comments
-
ok I debbuged a more, I beleave that bc cannot a correct pkcs8 pem file out of a ML-DSA key, ie. if i compare a key https://asecuritysite.com/signatures/mldsa_js then they look much bigger than the bc generated ones |
Beta Was this translation helpful? Give feedback.
0 replies
-
also generates much bigger pem files. |
Beta Was this translation helpful? Give feedback.
0 replies
-
moved to a issue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
im propably messed up something but i hope you can help me.
org.bouncycastle.operator.OperatorCreationException: cannot create signer: unknown private key passed to ML-DSA
is it correct that Dilithium key have been stadartisied an the new nams is ML-DSA?
im a bit confused, a dilithum encoded keys lools like this
and a ml-dsa looks like this
this looks not ok for me, how could so small key repalce the other one? therefore i assume my assumtion the ml-dsa-* are the new dilitium keys is probably wrong.
Beta Was this translation helpful? Give feedback.
All reactions