Re: [TLS] TLS Proxy Server Extension

[Yoav Nir <[e-mail]>]

On 8/1/11 5:19 PM, "David McGrew" <[e-mail]> wrote:

>
>On Aug 1, 2011, at 12:15 AM, Yoav Nir wrote:
>>
>>
>> As for servers, it's possible to change the tls-proxy format in
>> ClientHello to have a "role" field that could be either "client" or
>> "proxy".
>
>a further thought in this direction.  The server could sign the
>extension that it gets from the proxy, and that signature could be
>returned to the client, along with the data that was signed.  This
>would give the client a strong confirmation that the server was aware
>of the proxy.   From a security standpoint, this is good.  From a
>deployability standpoint, it would require that servers are modified
>to understand the extension, which is not so good.

That depends on what the clients do with this strong confirmation. For
example, I can see them showing the regular padlock even without the
signature, but displaying the EV indication only when they get it.

I'm also thinking about whether we can get client certificates to work.
The hard problem is that Certificate Verify signs the handshake messages,
and those are not available to the client. I don't think we want to send
all the previous handshake messages in the extension, so getting this to
work would also require a server-side change.

Yoav