#23: How can TLS clients match an SCT to a certificate? Changes (by [email protected]):
* milestone: => review Comment: Fixed by https://github.com/google/certificate-transparency- rfcs/commit/d71d7707a3eeb5707cf5048c3849b068e477038c The !ItemExtension field is gone. When there's a suitably name- constrained intermediate in the certificate chain, TLS clients may need to use trial and error to determine which of the certificates in the chain an SCT or inclusion proof corresponds to. -- ------------------------------+--------------------------------------- Reporter: [email protected] | Owner: [email protected] Type: defect | Status: new Priority: major | Milestone: review Component: rfc6962-bis | Version: Severity: - | Resolution: Keywords: | ------------------------------+--------------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/23#comment:11> trans <https://tools.ietf.org/trans/> _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
