Re: [TLS] drop obsolete SSL 2 backwards compatibility from TLS 1.3 draft

[Dave Garrett <[e-mail]>]

On Monday, December 29, 2014 06:58:43 am Martin Rex wrote:
> JDK 1.6 might be past its "End of Public Updates", but it is still
> fully supported and pretty omnipresent, in particular in company
> environments and the majority of server-side (J2EE) installations.

Server-side usage would not be affected by the proposed changes. TLS 1.3 clients 
would be sending v3 hellos which would be read just fine.

Server and client usage in company environments are where it is easiest to deal 
with the proposed changes. The clients' settings just need to be changed to stop 
using SSL entirely and send only v3 hellos.

I'll restate again, this is already the consensus.
(again, assuming no surprises with the SSL3 I-D)

http://tools.ietf.org/html/rfc6176
http://tools.ietf.org/html/draft-ietf-tls-sslv3-diediedie-00

To directly quote RFC 6176 (2011):
"TLS clients MUST NOT send the SSL version 2.0 compatible CLIENT-
HELLO message format"

With both SSL2 & SSL3 prohibited, there should be no v2 hellos.

Put bluntly, any environment that actually HAS v2 hellos is already ignoring 
IETF RFCs. They will potentially ignore the proposed change for this RFC. They 
cannot be the basis for decisions on what gets into new RFCs.


Dave