Re: [TLS] TLS renegotiation issue

[Nicolas Williams <Nicolas.Williams at sun.com>]

On Fri, Nov 06, 2009 at 12:51:59AM +0100, Martin Rex wrote:
> Nicolas Williams wrote:
> > 
> > On Thu, Nov 05, 2009 at 10:16:11AM -0800, Eric Rescorla wrote:
> > > I now have a draft extension up at:
> > > 
> > > https://svn.resiprocate.org/rep/ietf-drafts/ekr/draft-rescorla-tls-renegotiate.txt
> > > https://svn.resiprocate.org/rep/ietf-drafts/ekr/draft-rescorla-tls-renegotiate.xml
> > > 
> > > Comments welcome.
> > 
> > More comments:
> > 
> >  - Consider an implementation like Windows' SSPI-based implementation.
> >    Or, for that matter, the old GGF (Global Grid Forum) GSS-API
> >    interface to TLS.
> 
> This strikes me as really odd!

What's odd?

> Btw. does GGF really require renegotiation?  What is so impossible
> about asking for a client cert in the initial TLS handshake?

Did I say that?  No.  Please don't read into what I wrote.

But note that with a GGF GSS-API-based implementation of TLS you _can_
do re-negotiation!  It's simple really.  And it shows that there's no
link between the inner and outer connections (here, security contexts),
except that the outer one protects the inner's hanshake (here, security
context token exchange).  (Well, also, the app needs to know if the
server sent a ChangeCipherSpec message, so that it can switch to using
the inner security context for all subsequent wrap tokens.)

Nico
--