Opened 6 years ago

Closed 5 years ago

Last modified 4 years ago

#8214 closed enhancement (fixed)

openssl-1.1.0

Reported by: Douglas R. Reno Owned by: DJ Lucas
Priority: low Milestone: hold
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New major version.

One security fix that is notable:

  *) To mitigate the SWEET32 attack (CVE-2016-2183), 3DES cipher suites
     have been disabled by default and removed from DEFAULT, just like RC4.
     See the RC4 item below to re-enable both.
     [Rich Salz]

See the following resources:

https://sweet32.info/

https://www.openssl.org/news/changelog.html#x1

Change History (17)

comment:1 by Douglas R. Reno, 6 years ago

Milestone: 7.117.10

Allowing into 7.10 milestone. Please put into 7.11 if there are any objections.

comment:2 by ken@…, 6 years ago

From their Downloads page:

Note: The latest stable version is the 1.1.0 series of releases. Also available is the 1.0.2 series. This is also our Long Term Support (LTS) version (support will be provided until 31st December 2019). The 1.0.1 version is currently only receiving security bug fixes and all support will be discontinued for this version on 31st December 2016. The 0.9.8 and 1.0.0 versions are now out of support and should not be used.

comment:3 by Armin K, 6 years ago

I suggest sticking to 1.0.2 for 7.10. This release has many API breaks.

See also:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827061

Last edited 6 years ago by Armin K (previous) (diff)

comment:4 by bdubbs@…, 6 years ago

Milestone: 7.107.11

OK, moving this ticket to 7.11.

comment:5 by Igor Živković, 6 years ago

This might be a good opportunity to consider replacing it with libressl.

comment:6 by Douglas R. Reno, 6 years ago

Owner: changed from blfs-book@… to Douglas R. Reno
Status: newassigned

I'll take this challenge on. The SWEET32 issue needs to be mitigated.

comment:7 by Douglas R. Reno, 6 years ago

After doing some research, I have some information in terms of compatibility already, thanks to Armin's link to the Debian bug.

I can identify based on the Debian page that the following packages will have issues:

PHP
libevent
p11-kit
OpenSSH
Cyrus-SASL
Ruby
QCA
Unbound
sendmail
PulseAudio
ldns
PostgreSQL
Postfix
Qupzilla
MIT Kerberos V5 (krb5)
Apache (httpd)
gst-plugins-bad
wpa_supplicant
ntp
dovecot
Python3
fetchmail
re-alpine
hexchat
bind
qt5
neon
ptlib
nmap
qterm (qterminal?)
transmission
curl
wget
links

Based on the above, the following packages are unknown, and I will discover whether or not they might have issues once I get to them.

git
ruby
openjdk
*some* Perl Module (I'll look later)
python2
libarchive
libesmtp
apr-util
ptlib
ffmpeg
mplayer
w3m
lynx
wireshark
mutt
mailx
tripwire
Certificate Authority Certificates
gnutls
nettle
liboauth
stunnel
mariadb
vsftpd
proftpd
openldap
postfix
exim
xorg-server
seamonkey
firefox
thunderbird
xchat
balsa
libreoffice

comment:8 by Douglas R. Reno, 6 years ago

Milestone: 7.11hold
Priority: highlow

Moving to hold. There is no possible way to get this working with applications such as OpenSSH. The API changes with regards to DSA and RSA encryption have made it so that a significant amount of refactoring must be done. There was a message in July that stated that the OpenSSH folks would be working on it after the "7.3" release. This is a holdup for all other distros currently as well.

in reply to:  6 comment:9 by DJ Lucas, 6 years ago

Replying to renodr:

I'll take this challenge on. The SWEET32 issue needs to be mitigated.

https://www.openssl.org/blog/blog/2016/08/24/sweet32/ OpenSSL folks rated it low priority in the above review. I'm inclined to agree with their assessment given the amount of data required (and default configs of both httpd and nginx). I do not like the fix in 1.1.0. In the interim, we could safely follow the same approach as upstream until 1.0.2i is released if it is still a concern: https://github.com/openssl/openssl/commit/0fff5065884d5ac61123a604bbcee30a53c808ff The above classifies it as MEDIUM instead of HIGH. Optionally, we could move it to WEAK but still build 3DES via the enable-weak-ssl-ciphers switch (I don't like this).

When we do upgrade to 1.1.0, do we want to include 3DES anyway? Probably going to break some existing configs if not (which should be updated if not cost prohibitive). If not undoing the change in favor of the one for 1.0.2, at very least, the switch should be mentioned in command explanations. For reference, here is the 1.1.0 change (make it WEAK and not built by default): https://github.com/openssl/openssl/commit/d33726b92e09605a088369d0e01c99d138c0524f

Regarding Sweet32, no need to do anything with httpd or nginx configs for now. It is mathematically impossible to exploit using this method in the default configuration for both (maximum requests at 100).

comment:10 by DJ Lucas, 6 years ago

Oops, there were two changes associated with this in 1.1.0. https://github.com/openssl/openssl/commit/ef28891bab7054667f2f6739f6d376c38b3ca1cc

comment:11 by ken@…, 6 years ago

mutt-1.7.2 release announcement says

This is a bug fix release, primarily fixing build issues with OpenSSL
1.1 and GPGME 1.8

so mutt should be ok for this in a few hours.

comment:12 by Douglas R. Reno, 6 years ago

Owner: changed from Douglas R. Reno to blfs-book@…
Status: assignednew

If anyone else wants to do this, go ahead. I'm done.

comment:13 by DJ Lucas, 5 years ago

Update: looks like patches are outstanding for only NodeJS, OpenSC, Ruby, and QT. QT will release 5.9.0 on May 31st. If the remaining three packages are not capable of using OpenSSL-1.1 at that time, we could install OpenSSL-1.0.2k(?) libraries and headers in private directories and link with -rpath.

Regardless, this will not be a drop in replacement. Everything linked to OpenSSL will need to be rebuilt, some packages with additional patches. Will reevaluate for inclusion in early June.

comment:14 by DJ Lucas, 5 years ago

Owner: changed from blfs-book@… to DJ Lucas
Status: newassigned

comment:15 by bdubbs@…, 5 years ago

Milestone: holdy-hold

Milestone renamed

comment:16 by DJ Lucas, 5 years ago

Resolution: fixed
Status: assignedclosed

Fixed in r18783.

comment:17 by Bruce Dubbs, 4 years ago

Milestone: y-holdhold

Milestone renamed

Note: See TracTickets for help on using tickets.