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
Using the version 1.79 of BouncyCastle Java libraries, I noticed on one hand that a certificate chain validation CertPathValidator.validate() does a lot through but doesn't verify the alternative signature (if present of course). On the other hand, the method X509CertificateHolder.isAlternativeSignatureValid() is checking the alternative signature.
Now for hybrid certificates (that contains both a regular ECDSA signature and an alternative PQC signature like ML-DSA), my understanding is that the certificate verification should / might check both signatures.
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
Uh oh!
There was an error while loading. Please reload this page.
-
Hello BouncyCastle community !
Using the version 1.79 of BouncyCastle Java libraries, I noticed on one hand that a certificate chain validation CertPathValidator.validate() does a lot through but doesn't verify the alternative signature (if present of course). On the other hand, the method X509CertificateHolder.isAlternativeSignatureValid() is checking the alternative signature.
Now for hybrid certificates (that contains both a regular ECDSA signature and an alternative PQC signature like ML-DSA), my understanding is that the certificate verification should / might check both signatures.
Am I correct and if so is there a way to do it ?
Thanks
Sebastien
Beta Was this translation helpful? Give feedback.
All reactions