STM1 and STM2 certificates aren't parseable about go-tspi HOT 1 CLOSED

FYI, currently this is the only thing found for the search nuvoton "illegal padding" certificate.

The problem is this (at least on the certificates I've managed to inspect): the serial number is not canonically encoded as DER. This happens with a frequency matching what one would expect if Nuvoton's encoder simply generates 8 bytes of randomized serial numbers and then encodes that as an 8-byte INTEGER, and sometimes the first 9 bits of the serial number end up being all zeros or all ones, and this is an encoding error.

There is also a second non-canonical encoding error that I believe OpenSSL doesn't check for, and that is that the attributes of the subject name, which are in a SET OF, are not sorted as they should be.

These certificates are broken, but some relying parties will accept them, just not all of them.

In principle you can ask Nuvoton to re-issue any such broken certificates, since they could validate their own signature and re-sign a properly encoded certificate with otherwise all the same values, or at the very least the same subject public key.

from go-tspi.