Hi,
thank you for your report and helping to make Ubuntu better.
it might be totally true that some issue affects the connectivity of
some browsers - like the one of the cellphone you mentioned. But I'd
question the test you used in regard to TLSv1 support.
But IIRC that list just means that by default it is using TLSv1.2.
This isn't some sort of regression (here Trusty):
lxc exec trusty-tests -- openssl ciphers -v | awk '{print $2}' | sort | uniq
SSLv3
TLSv1.2
Also I can on Xenial just nicely connect via TLSv1, TLSv1.1 and TLSv1.2
openssl s_client -connect www.example.com:443 -tls1
CONNECTED(00000003)
[...]
Protocol : TLSv1
[...]
Verify return code: 0 (ok)
openssl s_client -connect www.example.com:443 -tls1_1
CONNECTED(00000003)
[...]
Protocol : TLSv1.1
[...]
Verify return code: 0 (ok)
openssl s_client -connect www.example.com:443 -tls1_2
CONNECTED(00000003)
[...]
Protocol : TLSv1.2
[...]
Verify return code: 0 (ok)
I'd expect that some part of your stack disabled TLSv1 and/or TLSv1.1
for security reasons as they are deprecated for quite some time now.
** Changed in: openssl (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636124
Title:
openssl lacks support for TLSv1 and TLSv1.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1636124/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
