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:
When test tls enabled uri with sasl connection, it will hang without feedback
Version-Release number of selected component (if applicable):
kernel-2.6.32-171.el6.x86_64
libvirt-0.9.4-0rc1.el6.x86_64
qemu-kvm-0.12.1.2-2.172.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Edit /etc/libvirt/libvirtd.conf
-- enbale listen_tls = 1
-- enable auth_tls = "sasl"
2. generate key and cert file to configure tls environment
3. service libvirtd stop; libvirtd -d --listen
4. saslpasswd2 -a libvirt -d fred
5. virsh -c qemu+tls://{ip}/system
Actual results:
will hang
Expected results:
continue by inputting authenticate user
Additional info:
Are you sure how your certs are proper. 0.9.4 now does some checks for
correctness of certificates and if your certificate are improper
libvirtd may not start, and you will see an error in libvirtd.log
Is there any informations about certificate being improper in libvirtd.log ?
Daniel
Hi DV,
If I change the auth_tls to 'none', then no problem. libvirtd start normally. When I change auth_tls to 'sasl', then it will hang. If only change libvirt version to 0.8.7-18 without any other changes, it will normal with asking :Please enter your authentication name. There is no error info in libvirtd.log
commit 8329c56e3a2017399f465aeca06ffa0039e2141a
Author: Guannan Ren <gren>
Date: Thu Aug 4 21:27:52 2011 +0800
rpc:fix sasl session relocking intead of unlocking it
When trying to use any SASL authentication for TCP sockets by
setting auth_tls = "sasl" in libvirtd.conf on server side, the
client will hang because of the sasl session relocking other than
dropping the lock when exiting virNetSASLSessionExtKeySize()
* src/rpc/virnetsaslcontext.c: virNetSASLSessionExtKeySize drop the
lock on exit
Description of problem: When test tls enabled uri with sasl connection, it will hang without feedback Version-Release number of selected component (if applicable): kernel-2.6.32-171.el6.x86_64 libvirt-0.9.4-0rc1.el6.x86_64 qemu-kvm-0.12.1.2-2.172.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Edit /etc/libvirt/libvirtd.conf -- enbale listen_tls = 1 -- enable auth_tls = "sasl" 2. generate key and cert file to configure tls environment 3. service libvirtd stop; libvirtd -d --listen 4. saslpasswd2 -a libvirt -d fred 5. virsh -c qemu+tls://{ip}/system Actual results: will hang Expected results: continue by inputting authenticate user Additional info: