On Fri, Mar 28, 2014 at 03:11:46PM -0400, Hubert Kario wrote:
> > I am much more concerned about servers than clients, but it is
> > likely that TLS client apps on XP (perhaps Outlook Express, ...)
> > also have similar problems.
>
> From what I found through googling I see that the issue was actually
> fixed quite a few years ago.
In theory only. The fix was very thinly applied, and is no longer
available for download.
> I don't think we should put known weak ciphers in future version of
> openssl's DEFAULT set to work with software configuration that is not
> supported by the vendor right now and won't be supported at all in just
> over a year.
You're still playing "my security level is bigger than yours".
There is no benefit in excluding RC4-SHA1 from the default list.
When servers support stronger algorithms, those will be negotiated.
All you get by exclusing RC4-SHA1 is loss of interoperability, which
may be OK for dedicated environments, but is not a good DEFAULT.
> And since current order already puts 3DES before RC4, people that
> need to workaround this issue, already know about it, so even if they
> update to future openssl version, they know the solution. The workaround
> won't change.
Except that the Microsoft servers in question elect RC4 ahead of
3DES even when the client lists 3DES first. Disabling RC4 is
typically counter-productive. You feel better about your security,
but mostly you've just reduced interoperability.
--
Viktor.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
