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.
Description of problem:
Validate empty host subject from qemu exactly like when no explicit host subject is specified
Version-Release number of selected component (if applicable):
spice-gtk-0.13.29-3.el6.x86_64
How reproducible:
always
Steps to Reproduce:
0, commont to both: generate CA and server certs to that CN= field in server cert subject matches your machine hostname (e.g Subject: O=rh,CN=my-laptop.example.com)
A: plain connection:
1. run qemu:
qemu-kvm -spice tls-port=SPORT,x509_dir=DIR,disable-ticketing
2. connect to the qemu:
remote-viewer --spice-ca-file DIR/ca-cert.pem spice://my-laptop.example.com/?tls-port=SPORT
B: migration
1. run source qemu:
qemu-kvm -monitor stdio -spice tls-port=SPORT1,x509_dir=DIR,disable-ticketing
2. run destination qemu:
qemu-kvm -monitor stdio -spice tls-port=SPORT2,x509_dir=DIR,disable-ticketing
3. connect to the source qemu:
remote-viewer --spice-ca-file DIR/ca-cert.pem spice://my-laptop.example.com/?tls-port=SPORT1
4. instruct source qemu to migrate the client without specifying host subject:
__com.redhat_spice_migrate_info my-laptop.example.com 0 SPORT2
Actual results:
A: r-v connects successfully because my-laptop.example.com FQDN matches CN in the certificate
B: r-v won't connect to the destination qemu with error:
(/usr/bin/remote-viewer:21596): Spice-Warning **: ssl_verify.c:484:openssl_verify: ssl: subject '' verification failed
Expected results:
A: the same
B: r-v should treat empty host subject as no host subject and verify CN= from Subject field with hostname
Additional info:
Comment 2Marc-Andre Lureau
2012-10-18 17:42:45 UTC
patch sent to ML
Comment 3Marc-Andre Lureau
2012-12-10 13:00:50 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-0343.html