[FFe] openssl 1.1.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| openssl (Ubuntu) |
Undecided
|
Unassigned | ||
| python2.7 (Ubuntu) |
Undecided
|
Unassigned | ||
| python3.6 (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Merge openssl 1.1.1 from debian unstable.
OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release.
Resulting in the following changes in Ubuntu:
- openssl moves from 1.1.0 series to 1.1.1 LTS series
- TLS1.3 is enabled, and used by default, when possible. Major feature.
- All existing delta, and minimally accepted key sizes, and minimally accepted protocol versions remain the same.
Proposed package is in https:/
===
Ubuntu delta summary versus debian unstable in this merge:
- Replace duplicate files in the doc directory with symlinks.
- debian/
+ Display a system restart required notification on libssl1.1
upgrade on servers.
+ Use a different priority for libssl1.
on whether a desktop, or server dist-upgrade is being performed.
- Revert "Enable system default config to enforce TLS1.2 as a
minimum" & "Increase default security level from 1 to 2".
- Further decrease security level from 1 to 0, for compatibility with
openssl 1.0.2.
These mitigate most of the runtime incompatibilities, and ensure client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series and thus one can continue to mix & match xenial/
tags: | added: needs-debian-merge upgrade-software-version |
Marc Deslauriers (mdeslaur) wrote : | #1 |
description: | updated |
Steve Langasek (vorlon) wrote : | #2 |
Please express the FFe in terms of what will change relative to the current Ubuntu package, not relative to the Debian package.
Changed in openssl (Ubuntu): | |
status: | New → Incomplete |
description: | updated |
Changed in openssl (Ubuntu): | |
status: | Incomplete → New |
Dimitri John Ledkov (xnox) wrote : | #3 |
@steve updated. Ping?
Steve Langasek (vorlon) wrote : | #4 |
+1 on this FFe based on the analysis provided. I do not consider interoperability issues a reason not to turn on TLS1.3 in FFe; it will eventually be turned on and expose those issues, and whether it happens post-FF or before FF in 18.10, or post 18.10 release, is immaterial.
Changed in openssl (Ubuntu): | |
status: | New → Confirmed |
tags: | added: block-proposed |
Dimitri John Ledkov (xnox) wrote : | #5 |
Pythons appear to hardcode the expectations relative the openssl they were built with, despite not gaining >= 1.1.1 shlibsdep, somehow it ends up with >= 1.1.0 only.
Dimitri John Ledkov (xnox) wrote : | #6 |
ruby2.5 ruby-openssl python3.7 correctly gain stronger dep on libssl1.1 >= 1.1.1.
python2.7 and python3.6 still need more patches to pick up https:/
no longer affects: | ruby2.5 (Ubuntu) |
no longer affects: | python3.7 (Ubuntu) |
Łukasz Zemczak (sil2100) wrote : | #7 |
Basing on the comment from Steve this is approved so switching status to Triaged.
Changed in openssl (Ubuntu): | |
status: | Confirmed → Triaged |
Łukasz Zemczak (sil2100) wrote : | #8 |
Switching the other tasks to Triaged as well since those changes are required for the base 1.1.1 feature to be completed.
Changed in python2.7 (Ubuntu): | |
status: | New → Triaged |
Changed in python3.6 (Ubuntu): | |
status: | New → Triaged |
Dimitri John Ledkov (xnox) wrote : | #9 |
Should hopefully land today... here be dragons
tags: | removed: block-proposed needs-debian-merge |
tags: | added: block-proposed |
tags: | removed: block-proposed |
Changed in openssl (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in python2.7 (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in python3.6 (Ubuntu): | |
status: | Triaged → Fix Committed |
Jeremy Bicha (jbicha) wrote : | #10 |
Changed in openssl (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in python2.7 (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in python3.6 (Ubuntu): | |
status: | Fix Committed → Fix Released |
Iain Lane (laney) wrote : | #11 |
systemd has "+ * Add conflicts with upstart and systemd-shim. (LP: #1793092)", but it's not straightforward to me what is going on here. Could you explain a bit more please?
Dimitri John Ledkov (xnox) wrote : | #12 |
wrong bug number typpo!
Big ACK from the security team. We would like to see this backported into bionic at some point and having it in cosmic first would allow us to identify and fix any issues.