Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause
Connection to spice-server secure_port is done by securing (using openssl) an unsecured connection (established using connect_unsecure function).
Consequence
Spice client log showed secure-connection messages containing "connect_unsecure"
Fix
The function that establish connection was renamed to connect_to_peer. Both secure and unsecure connections call this function.
Result
Spice client log shows secure-connection messages containing "connect_to_pee
r" and does not contain "unsecure".
Description of problem:
The log shows that the connection is unsecured instead of secured.
Version-Release number of selected component (if applicable):
[ogvura@ogvura ~]$ rpm -q spice-client
spice-client-0.6.3-2.el6_0.3.x86_64
[ogvura@ogvura ~]$ rpm -q spice-xpi
spice-xpi-2.4-1.el6.x86_64
Steps to Reproduce:
1. Connect to the VM via spicec
2. Run the command: cat .spicec/spicec.log
Actual results:
Getting the Error print: (RedPeer::connect_unsecure: Trying 10.35.64.95 5885 )
Expected results:
Changing the error to be secured.
Ortal, please attach complete log.
The problem is that the connection (2 out of the 6 or so channels) are actually TLS secured. Nevertheless, all the logs are connection_*unsecure*
Comment 11Christophe Fergeau
2011-07-04 16:46:13 UTC
It looks like the patch mentioned in this bug hasn't been applied yet, even though it was ACK'ed on the mailing list. I think this bug should be devel_ack+ and the patch committed to spice git.
Comment 12Christophe Fergeau
2011-07-08 11:38:01 UTC
VERIFIED in spice-client-0.8.2-7:
1318595180 INFO [16959:16960] RedPeer::connect_unsecure: Connected to 10.34.58.4 5904
1318595180 INFO [16959:16960] RedPeer::connect_secure: Connected to 10.34.58.4 5905
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
Connection to spice-server secure_port is done by securing (using openssl) an unsecured connection (established using connect_unsecure function).
Consequence
Spice client log showed secure-connection messages containing "connect_unsecure"
Fix
The function that establish connection was renamed to connect_to_peer. Both secure and unsecure connections call this function.
Result
Spice client log shows secure-connection messages containing "connect_to_pee
r" and does not contain "unsecure".
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-2011-1518.html