Re: More fun and games with the Trusted Platform Module
Russ Housley <[email protected]>
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Message-ID | <[email protected]> |
So, the INTEGER is not being properly DER encoded before it is stored. I assume the signature covers the leading zero octet. Russ > On Feb 13, 2018, at 8:56 PM, Michael StJohns <[email protected]> wrote: > > Hi - > > I thought I'd pass on a discovered stupidity. As part of some playing with TPMs I found out that the endorsement certificate for my personal laptop has an invalid encoding. For some unknown reason, my certificate was mis-encoded with a leading zero byte in the serialNumber field. My best guess is that the manufacturer is mistakenly treating the serialNumber as an OCTET STRING and just plopping down the serial number of the TPM in the body of the INTEGER. > > Unfortunately, the certificate parsers I'm using barf on this..... I'm having to basically write my own code to handle these... > > serial: > > 02 14 > 00 04 8f e6 1d 28 82 d3 cd 48 8a b1 30 b9 4f bc > 8928 4b 32 > > According to the TPM console, this is an intel TPM, V2.0, spec 11.8.50.3425. > > I went looking and I have no contacts with Intel in this space - I'd at least like to make them aware they are screwing up in at least one case. Does anyone have a pointer? > > Thanks - Mike > > > _______________________________________________ > pkix mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/pkix _______________________________________________ pkix mailing list [email protected] https://www.ietf.org/mailman/listinfo/pkix