Hide Forgot
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:
it can success on libvirt-0.8.7-18, so it is a regression bug
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
*** Bug 728053 has been marked as a duplicate of this bug. ***
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
*** This bug has been marked as a duplicate of bug 729198 ***