Re: [TLS] I-D Action: draft-ietf-tls-negotiated-ff-dhe-10.txt

[Jeffrey Walton <[e-mail]>]

On Wed, Jun 3, 2015 at 4:50 PM, Tony Arcieri <[e-mail]> wrote:
>
>
> On Wednesday, June 3, 2015, Dave Garrett <[e-mail]> wrote:
>>
>> The topic brought up by Tony Arcieri was the apparent plague of old Java
>> clients using TLS currently. A replacement set of cipher suites would
>> transparently fix this in a simpler way. It adds more suites, yes, but it
>> would ensure that this is only ever even _attempted_ to be negotiated
>> between clients and servers that both support them properly.
>
>
> That's "half the battle", IMO, and I think the other half of my argument was
> lost in a swarm of "LOL Java, there's your problem" responses. I also called
> out the "what about a catastrophic ECC failure?" in advance and yet that is
> somehow the main "pedantic" response I've been receiving to my complaints.
>

One thing to keep in mind with the Java clients...

   SSLSocketFactory.getInstance("TLS");

will return a socket with SSLv3 and TLS 1.0 enabled. You will also get
the cipher suite zoo enabled. TLS 1.1 and 1.2 were even disabled for
Java 7 (Java 8 finally enabled them).

You have to jump through hoops to get something sane, like "TLS 1.0
and above with reasonable cipher suites". See, for example,
http://stackoverflow.com/a/23365536/608639.

So its not clear you would get desired behavior regardless of what
happens. Old clients won't get the updates, and old and new code often
won't utilize seek out desired socket behavior.

Jeff