Re: [TLS] Comments on TLS identity protection

Eric Rescorla wrote:
> 
> "Kyle Hamilton" <aerowolf@gmail.com> writes:
> > On every renegotiation, does the server have to reauthenticate itself
> > (present its certificate again)?  Or can the credential on the client
> > side be cached to avoid that duplication?
> 
> I don't think I understand the question.
> 
> 1. You do a regular handshake with no client auth.
>
> 2. The server initiates a rehandshake with client auth. This has
>    to be a full handshake with a new key exchange.
> 
> Any future resumptions of the second session can be done out
> of cache.

When the server-requested renegotiation is application triggered,
as in the Microsoft IIS case, then the server better caches the
result along with the SSL session.

Microsoft IIS has a silly (performance-wasting) bug, where a client that
does either not have a client cert or does not show one (and requiring
the application to perform application level client authentication)
is continously forced through the renegotiation when the client
tries to resume the session from the session cache on a new connection.

-Martin

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls