[Bug 965371] Re: HTTPS requests fail on sites which immediately close the connection if TLS 1.1 negotiation is attempted, on Ubuntu 12.04
Adam Porter
965371 at bugs.launchpad.net
Sat Jul 7 21:31:30 UTC 2012
On Sat, Jul 7, 2012 at 8:50 AM, Marc Deslauriers
<marc.deslauriers at canonical.com> wrote:
> So the whole world is moving to TLS 1.1 and 1.2, and Evernote's server
> isn't compatible. How is this a Ubuntu bug?
I'm no expert on TLS, but surely it's an exaggeration to say that the
whole world is moving to 1.1 and 1.2. This exact issue can be found
in reports on mailing lists (including openssl's) going back at least
two years. The whole issue arises because of a failed backward
negotiation by the server. When are these servers (Apache and PHP, in
Evernote's case), which currently fail to fall backwards, going to
start rejecting clients who do the same? Are they really going to
drop like a hot rock browsers which can't even request TLS 1.1 or 1.2,
browsers which will necessarily be in use for many more years? (You
must consider enterprise installations, proprietary software, and
embedded software which won't be even upgraded until the hardware is
replaced.) Last I checked, HTTP 1.1 was not required on any web
sites--1.0 works fine. SSL still works too, so why would TLS 1.0 be
dropped?
> What do you propose we do? Disable TLS 1.1 and 1.2, which will prevent
> Ubuntu from working with newer sites that will start requiring it, just
> to fix Evernote's broken server?
If there are servers which commonly refuse SSLv3 and TLS 1.0 and
require TLS 1.1 or 1.2, please let me know--again, I'm no expert. Or
are users actually at risk by not having support for protocols which
may not even work? Are there such serious security flaws in TLS 1.0?
(If so, why do servers support it and even SSL?)
Lacking examples of such, what we have is a known problem in which
user software utterly fails after upgrading the OS, in which the only
workaround is to reinstall and downgrade the entire OS--versus a
potential benefit of supporting newer versions of a protocol which
many servers don't even support yet, and indeed fail on.
If it's not that clear-cut, please explain why. Otherwise, the choice
seems obvious to me: disable TLS 1.1 and 1.2 by default so that Ubuntu
users who have upgraded to "Precise 12.04 Long Term Support" will not
have their software mysteriously fail without recourse. If the
situation changes at a later time, whether by an upgrade to OpenSSL
which works around broken servers, or if broken servers truly
disappear from the Internet, then 1.1 and 1.2 could be reenabled.
As I have always understood it, the point of a distro is to make
software work for the user. So, yes, I propose that you disable TLS
1.1 and 1.2 by default.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/965371
Title:
HTTPS requests fail on sites which immediately close the connection if
TLS 1.1 negotiation is attempted, on Ubuntu 12.04
Status in OpenSSL cryptography and SSL/TLS toolkit:
Confirmed
Status in “openssl” package in Ubuntu:
Triaged
Status in “openssl” source package in Precise:
Triaged
Status in “openssl” package in Debian:
Fix Released
Bug description:
This week, HTTPS connections from a Python script I wrote started
giving me this error:
urllib2.URLError: <urlopen error [Errno 8] _ssl.c:497: EOF occurred in
violation of protocol>
This used to work up until some three days ago and still works on
other Ubuntu versions, but not in other Python versions on Precise. I
was suspecting this was a bug in Python, but a guy on AskUbuntu (
http://askubuntu.com/questions/116020/python-https-requests-urllib2
-to-some-sites-fail-on-ubuntu-12-04-without-proxy/116059#116059 )
found out this happens using the openssl command line tool too:
$ openssl s_client -connect www.mediafire.com:443
But succeeds if forcing TLS 1 with the -tls1 argument.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/965371/+subscriptions
More information about the foundations-bugs
mailing list