Re: [TLS] [CHANNEL-BINDING] [sasl] Updates to draft-altman-tls-channel-bindings, take two (PLEASE REVIEW)

[Nicolas Williams <[e-mail]>]

On Tue, Mar 23, 2010 at 02:06:29PM -0500, Nicolas Williams wrote:
> It occurs to me that it must be very unlikely that any apps using the
> MSFT variant of tls-unique are doing authentication after TLS
> re-negotiation.  We already have confirmation that in the HTTP/Negotiate
> case that never happens.  If so, might you be willing to fix your
> implementation to always use the initial handshake?  That would help
> remove two pieces of complexity from -09: a) security considerations with
> regard to the TLS re-negotiation bug, b) interoperability considerations
> with regard to the channel binding synchronization problem.

I need to re-word my question to clarify that I'm not interested in
knowing what MSFT proprietary apps you're using CB in.  Does TLS
re-negotiation ever occur prior to authentication in any of your
applications?  I'm NOT interested in knowing anything else about
proprietary MSFT applications, just that one detail about Internet as
well as proprietary apps.

The point of the question is to establish whether we really have to pick
the first Finished message of the latest/inner-most handshake or if
there's still time for you to fix your implementation so that we can use
the first Finished message of the first/outer-most handshake.

Nico
--