Issue With OQS-Chromium about oqs-demos HOT 5 CLOSED

Thanks for the test and the complete description of your setup! Based on this, two questions:

Since the root certificate has been installed and the verification of root certificate - intermediate certificate chain doesn't require any OQS-enabled library, the website should be accessible in Chromium.

Why are you expecting this? Chromium ought to verify the whole cert chain, incl. the dilithium-site cert and not just the "last step". Hence #92 (and the errors shown) are to be expected, as there is a QSC alg involved, right?

We further found that Chromium failed to verify the root certificate - intermediate certificate chain, but it succeeded in verifying the intermediate certificate - leaf certificate chain.

How did you come to this conclusion/what test did you do? I would actually expect the exact opposite: The intermediate cert could/should be verifiable with classic crypto while the site/leaf->intermediate cert needing QSC should not be as per #92.

from oqs-demos.

The intermediate cert could/should be verifiable with classic crypto while the site/leaf->intermediate cert needing QSC should not be as per #92.

I've thought about this reason. What is really confusing is that there is no root certificate in the Chromium Certificate Viewer hierarchy. I initially thought this was due to I didn't supply the root certificate in the certificate chain, so I modified nginx server config and added the root certificate in the certificate chain and the root certificate still didn't appear in the Certificate Viewer hierarchy.

If this is the reason, why Chromium Certificate Viewer shows the intermediate certificate? Both intermediate certificate and root certificate shouldn't appear in the Certificate Viewer hierarchy as the chain already broke at leaf - intermediate.

from oqs-demos.

If this is the reason, why Chromium Certificate Viewer shows the intermediate certificate?

I don't know this -- probably one would need to go through the cert verification logic of Chromium (nss) to really understand what's going on. Personally I didn't get around to looking into libnss to be able to give a good answer.

from oqs-demos.

Good suggestion.

from oqs-demos.

As it seems this issue indeed is caused by libnss not being QSC-enabled we'll close this issue referring to #92 for further discussions/activity. Please feel free to re-open this with further feedback if you don't think likewise, @Raytonne. Thanks again for your test & report!

from oqs-demos.