3 ms·
Do we know that MS TLS implementation parses self-signed certs only after successful validation? Many implementations offer an option of showing their contents
by fulafel 7y ago
Do we know that MS TLS implementation parses self-signed certs only after successful validation? Many implementations offer an option of showing their contents (eg to see what CA it claims to be signed by), or offer the user a choice to accept it, or log identifying fields from the cert for diagnostic purpouses. Same for the CA server offered CA chain.
I'm also not convinced that the fields-allowed-by-CAs set is safe, especially when you consider the set of all browser-accepted CAs, it's historically been a fraught field.
Also with x.509 you have to decode the ASN.1 before you can even get to the signature, there have been historically been lots of vulnerabilities in ASN.1 parsers.
- cjbprime 7y ago> Do we know that MS TLS implementation parses self-signed certs only after successful validation? It would be a contradiction in terms. You can't validate the semantic content of a file before you've parsed it!
- fulafel 7y agoYeah, I should have said "before it processes any other fields". The ASN.1 parse of course comes first.