Re: [TLS] stapling OCSP/CT for client cert?

On Wed, Feb 22, 2017 at 05:23:22PM +, David Benjamin wrote: > Looks like TLS 1.3 already allows this for CT, though not OCSP. Would take > all of four characters to fix. See this table: > https://tlswg.github.io/tls13-spec/#rfc.section.4.2 > > One of the nice things about using TLS-style exten

Re: [TLS] stapling OCSP/CT for client cert?

https://github.com/tlswg/tls13-spec/pull/880 I knew it was easy to fix, wasn’t sure if folks wanted it. Gives me a reason to join the contributors list. Very useful in peer-to-peer situations. ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mail

Re: [TLS] stapling OCSP/CT for client cert?

Looks like TLS 1.3 already allows this for CT, though not OCSP. Would take all of four characters to fix. See this table: https://tlswg.github.io/tls13-spec/#rfc.section.4.2 One of the nice things about using TLS-style extensions in CertificateRequest is any ClientHello => (Server)Certificate exte

[TLS] stapling OCSP/CT for client cert?

Any thoughts on being able to staple OCSP (or CT) data to a client cert once requested by the server? -- Senior Architect, Akamai Technologies Member, OpenSSL Dev Team IM: richs...@jabber.at Twitter: RichSalz ___ TLS mailing list TLS@ietf.org https://w