CUPS now disables SSLv3 encryption by default
Previously, it was not possible to disable SSLv3 encryption in the CUPS scheduler, which left it vulnerable to attacks against SSLv3. To solve this issue, the *cupsd.conf* `SSLOptions` keyword has been extended to include two new options, `AllowRC4` and `AllowSSL3`, each of which enables the named feature in *cupsd*. The new options are also supported in the */etc/cups/client.conf* file. The default is now to disable both RC4 and SSL3 for *cupsd*.
Created attachment 955007[details]
cups-str4476.patch (RHEL-7)
Here's the patch I plan to use.
It's a more or less straightforward back-port.
It augments the cupsd.conf "SSLOptions" keyword to include two new options, AllowRC4 and AllowSSL3, each of which enables the named feature in cupsd. The default is now to disable both RC4 and SSL3 for cupsd.
It also introduces the new /etc/cups/client.conf "SSLOptions" keyword, with options AllowRC4 and AllowSSL3. In order to enforce this correctly, the system-wide /etc/cups/client.conf file is read first, and the user ~/.cups/client.conf file (in which "SSLOptions" is not valid) is read afterwards. The default is now for clients to use neither RC4 nor SSL3.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2386.html