Bug 879352

Summary:	spice-gtk shouldn't ignore secure channels controller message and it should provide equivalent cli option
Product:	Red Hat Enterprise Linux 6	Reporter:	David Jaša <djasa>
Component:	spice-gtk	Assignee:	Marc-Andre Lureau <marcandre.lureau>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.4	CC:	acathrow, cfergeau, danken, dblechte, lnovich, marcandre.lureau, michal.skrivanek, pvine
Target Milestone:	beta
Target Release:	6.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spice-gtk-0.20-1.el6	Doc Type:	Bug Fix
Doc Text:	Cause: spice-gtk connects to the server plain port by default (succeeds only if server provides it). Consequence: spice-gtk can't be told to connect to secure port by default. Fix: Learn to connect only to secure port. Result: spice-gtk can be told to connect to secure port instead of always trying plain port first.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 08:24:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	905930

Description David Jaša 2012-11-22 16:34:07 UTC

Description of problem:
spice-gtk shouldn't ignore secure channels controller message and it should provide equivalent cli option

Version-Release number of selected component (if applicable):
spice-gtk-0.14-4.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. run qemu-kvm with both tls and plaintext ports listening but no default channel set
2a. connect from test page with some channel set to secure in the page
2b. try to specify the secure channel on the command line
  
Actual results:
a: spice-gtk-based client happily connects on plaintext port
b: there's no way to set the channels to be connected on secure port

Expected results:
spice-gtk should connect to tls-port right away and fail the whole connection if the channel connection fails (iow it should behave exactly the same as spicec)

Additional info:
plaintext channels should be possible to be specified the same way but there is lack of plugin and controller support for them: bug 879343. It would be nice to have this issue handled for them in one go however.

Note that this _is not_ a security issue as the tls channel enforcement is done primarily server side where there is no similar problem.

Comment 1 Marc-Andre Lureau 2013-04-12 02:24:33 UTC

Patches upstream.

Comment 2 Michal Skrivanek 2013-04-29 16:10:59 UTC

This is blocking bug 905930 which has a serious impact on RHEV SSO. The screen is locked whenever user connects. Currently the workaround in 905930 in 3.2 is to sleep for 2 seconds and if no other event comes just ignore the event. But that's clearly a very poor "solution"

Comment 10 errata-xmlrpc 2013-11-21 08:24:55 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.

http://rhn.redhat.com/errata/RHBA-2013-1577.html