Whilst debian is transitioning to openssl1.1, it is only partial
transition at the moment with many projects explicitly not supporting
openssl1.1 and forcing compilation against openssl1.0. In Ubuntu main,
the big ones are apache2, erlang, openssh, ruby, pam. Providing security
support for both openssl1.1 and openssl1.0 in main would increases
attack surface and result in mixed features (some components have
ability to use new crypto, whilst others don't). Thus we would like to
only have one openssl in main, and we have reverted the openssl1.1
transition in Ubuntu. Making openssl1.1 available, without making it the
default openssl is of limited benefit as none of the server packages
will use it and/or benefit from it.
Please note, 1.0.2 is LTS with upstream support until end of 2019.
Whilst 1.1.0 has a shorter cycle until end of August 2018.
Please help upstreams (apache2, openssh, erlang, ruby, pam-p11, etc.)
porting to openssl1.1.
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu)
Milestone: None => later
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
** Changed in: openssl (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1591833
Title:
[Featue] Upgrade Openssl for Intel QAT (quickassist-technology)
Status in intel:
New
Status in openssl package in Ubuntu:
Confirmed
Status in openssl package in Debian:
Confirmed
Bug description:
In order to support Intel QAT, please upgrade Openssl package from
1.0.2 to 1.1.0
HW: Purley-4s
Upstream schedule:
Openssl: 1.1.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1591833/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
