RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1175540 - Backport patches enabling TLS 1.1 and better to spice-server
Summary: Backport patches enabling TLS 1.1 and better to spice-server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 7.1
Assignee: Default Assignee for SPICE Bugs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-18 01:18 UTC by David Jaša
Modified: 2015-03-05 07:56 UTC (History)
5 users (show)

Fixed In Version: spice-0.12.4-9.el7
Doc Type: Bug Fix
Doc Text:
Cause: spice-server uses exclusively TLS version 1.0 for encrypted connections no matter what version(s) the client advertises. Consequence: newer versions of TLS cannot be used Fix: spice-server code was changed to allow TLS 1.0 or newer Result: clients can connect using versions of TLS newer than 1.0
Clone Of:
Environment:
Last Closed: 2015-03-05 07:56:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0335 0 normal SHIPPED_LIVE spice bug fix and enhancement update 2015-03-05 12:23:09 UTC

Description David Jaša 2014-12-18 01:18:26 UTC
Description of problem:
Backport patches enabling TLS 1.1 and better to spice-server. The patches were added in 0.12.5 but RHEL 7 still uses 0.12.4. RHEL 6 already features this patch since RHEL 6.6.

Version-Release number of selected component (if applicable):
0.12.4-8

How reproducible:
always

Steps to Reproduce:
1. connect to spice-server
2. look what TLS version is used (e.g. in Wireshark)
3.

Actual results:
version is TLS 1.0

Expected results:
version should be TLS 1.2

Additional info:
spice-server is the culprit, spice-gtk already updated to use SSLv23_method():
$ grep -rIsn 'TLSv1_method\|SSLv23_method' /usr/src/debug/spice*
/usr/src/debug/spice-0.12.4/server/reds.c:3242:    ssl_method = TLSv1_method();
/usr/src/debug/spice-gtk-0.22/spice-gtk-0.22/gtk/spice-channel.c:2285:        c->ctx = SSL_CTX_new(SSLv23_method());

Comment 1 Marc-Andre Lureau 2015-01-02 14:31:47 UTC
It seems the only patch required is:

commit 4fc9ba5f27dd4c04441d38c893ee962da01baf80
Author:     David Jaša <djasa>
AuthorDate: Wed Nov 27 17:45:49 2013 +0100
Commit:     Christophe Fergeau <cfergeau>
CommitDate: Thu Dec 12 10:39:11 2013 +0100

If qa is ok for a new build, I think this bug is important enought for 7.1 exception.

Comment 2 Marc-Andre Lureau 2015-01-05 20:37:07 UTC
Can it get exception+ too? David, this patch is already in 6.6, so I think it should also be in upcoming 7.1 release.

Comment 7 errata-xmlrpc 2015-03-05 07:56:38 UTC
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-0335.html


Note You need to log in before you can comment on or make changes to this bug.