Subject: [ietf-tls] Re: Re: Re: London

From: Bodo Moeller <[email-masked]>
Date: Mon, 16 Jul 2001 16:42:01 +0200

On Tue, Jul 17, 2001 at 01:52:03AM +1200, Peter Gutmann wrote:

>> If you disabled SSL 2.0 and enabled TLS 1.0 (the latter was disabled by
>> default), it did not use the SSL 3.0 ClientHello format as it should have
>> done, but the TLS 1.0 ClientHello format; that is, the record header contained
>> a 'version' value of {0x03, 0x01}, i.e. the 'client_version' value, while it
>> should contain {0x03, 0x00} for backwards compatibility.

> That's correct isn't it? RFC 2246 says:
> 
>   TLS clients who wish to negotiate with SSL 3.0 servers should send client
>   hello messages using the SSL 3.0 record format and client hello structure,
>   sending {3, 1} for the version field to note that they support TLS 1.0. If
>   the server supports only SSL 3.0, it will respond with an SSL 3.0 server
>   hello; if it supports TLS, with a TLS server hello. The negotiation then
>   proceeds as appropriate for the negotiated protocol.

'The version field' is singular, so this refers just to the version
field of the ClientHello message, i.e. client_version.

The complete wording 'sending {3, 1} for the version field to note
that they support TLS 1.0' also suggests that this is about
client_version, because client_version's purpose is to name
'the latest (highest valued) version supported by the client'.

The record header 'version' field names '[the] version of the protocol
being employed', i.e. 3.0 in this case.  Otherwise it would be the
TLS 1.0 record format, not the SSL 3.0 record format.

-- 
Bodo Möller <[email-masked]>
PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html
* TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt
* Tel. +49-6151-16-6628, Fax +49-6151-16-6036

---
You are currently subscribed to ietf-tls as: [email-masked]
To unsubscribe send a blank email to [email-masked]