You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are there plans to support post-quantum hybrid kems/signatures in bc with the recently nist standardized algorithms? In case there are, would the bc community allocate oids under bouncy castle or is there some mostly exhaustive list of allocated hybrid oids to import? I know that oqs-provider has some hybrid oids, but some more would have to be allocated if one would like to support all combinations from {mlkem*, mldsa*, slhdsa*} $\times$ {p256, p384, p521, curve25519, curve448} for example. What is the standard procedure for allocating oids like this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Are there plans to support post-quantum hybrid kems/signatures in bc with the recently nist standardized algorithms? In case there are, would the bc community allocate oids under bouncy castle or is there some mostly exhaustive list of allocated hybrid oids to import? I know that oqs-provider has some hybrid oids, but some more would have to be allocated if one would like to support all combinations from {mlkem*, mldsa*, slhdsa*}$\times$ {p256, p384, p521, curve25519, curve448} for example. What is the standard procedure for allocating oids like this?
Beta Was this translation helpful? Give feedback.
All reactions