OID displayed instead of signature algorithm name (MLDSA) in custom Chromium build

[prempatni1995]

I recently built Chromium following the instructions in oqs-demos/chromium.
The build completed successfully, and I was able to generate a working Chromium executable.

However, when I open a local HTTPS website (served via nginx) using an MLDSA self-signed certificate (specifically mldsa65), the certificate viewer in my custom Chromium displays only the OID for the signature algorithm—not the expected short_name or long_name of the algorithm.

Expected behavior

Chromium should display the algorithm’s readable name (e.g., the short or long name) instead of only the raw OID.

[pi-314159]

Thank you for reporting this. Nonetheless, it's not an urgent issue, so it won't be fixed anytime soon. If you'd like, you can try to fix it and submit a PR.