Re: [TLS] Triple Handshake Fix.

I've uploaded the draft to the IETF repository [1].

A tentative implementation of the fix for OpenSSL is available at [2].
(This patch currently also includes a "secure resumption" extension, which
would become unnecessary if the master secret derivation is fixed; I'm
willing to cleanup the patch if there's interest in it).

Cheers,
Alfredo

[1] http://www.ietf.org/id/draft-bhargavan-tls-session-hash-00.txt
[2]
https://secure-resumption.com/patches/OpenSSL1_0_1e-session_hash-extended_ms-secure_resumption.patch

On Tue, Apr 29, 2014 at 11:05 PM, Adam Langley <agl@google.com> wrote:

> Without a fix for the Triple Handshake issues[1], TLS Channel Bindings
> (at least tls-unique) have a significant problem, not to mention
> client-auth.
>
> Microsoft and ourselves are looking to implement the proposed fix[2]
> soon. I'd like to request that the WG adopt the draft and that the
> process for early codepoint assignment for the TLS extension start.
>
> I think the change to the master secret calculation is relatively
> uncontroversial (and is probably what the master secret should always
> have been). People might have differing opinions on the SCSV, but that
> doesn't affect whether a TLS extension number will ultimately be
> allocated for it.
>
>
> [1] https://secure-resumption.com
> [2] https://secure-resumption.com/draft-bhargavan-tls-session-hash-00.txt
>
>
> Cheers
>
> AGL
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>