A new meeting session request has just been submitted by Sean Turner, a Chair
of the tls working group.
-
Working Group Name: Transport Layer Security
Area Name: Security Area
Session Requester: Sean Turner
Number of Sessions: 2
Length
I've put together some PRs to address the comments from last call. Comments
welcome.
Failing CertificateVerify due to MITM text:
https://github.com/tlswg/tls-exported-authenticator/pull/28
Comments from Ben Kaduk:
https://github.com/tlswg/tls-exported-authenticator/pull/26
Authenticated Denial:
I've reviewed changes. Thanks for writing them up Nick.
Two concerns:
On #26, I think that there is a misunderstanding of how
signature_algorithms and signature_algorithms_cert work. My
understanding is that the former applies to the entire chain, unless
the latter is present, in which case the
On Tue, May 29, 2018 at 6:16 PM Jeffrey Walton wrote:
> I also delivered an OpenSSL-based TLS-LTS prototype to a Hoteliers
> working group for their smart locks last year. I have no idea how much
> of the code they are going to reuse (if any at all).
Chrome / Google is blocked on code-point assig
I agree we should use a different number than 26 for certificate
compression. I don't see a problem with assigning 27 and reserving 26 for
now.
On Wed, May 30, 2018 at 8:13 PM, Adam Langley
wrote:
> On Tue, May 29, 2018 at 6:16 PM Jeffrey Walton wrote:
> > I also delivered an OpenSSL-based TLS
