On 05/22/2012 10:04 AM, Martin Kletzander wrote:
[...]
> I'll have a look at it and fix it if it's like this.
Going through the docs, I realized I made a mistake and I've set up the
keys incorrectly (I should read more slowly and twice) and the
documentation is right. '*key*.pem' goes to '/etc/pki
On 05/21/2012 08:03 PM, Hubert Zhang wrote:
> https://www.redhat.com/archives/libvirt-users/2012-May/msg5.html
>
>
> When I run the sample code with the case of Python code for using qemu+tcp
> with SASL, I always got this SASL error:
>
> Traceback (most recent call last):
> File "esxLi
https://www.redhat.com/archives/libvirt-users/2012-May/msg5.html
When I run the sample code with the case of Python code for using qemu+tcp
with SASL, I always got this SASL error:
Traceback (most recent call last):
File "esxList.py", line 102, in ?
conn = libvirt.openAuth(uri, auth
On 05/02/2012 03:00 PM, John Wayne wrote:
Hi,
Can anyone please share sample Python code for using qemu+tcp with
SASL or qemu+tls with SASL? (i.e., connecting to a hypervisor using
qemu+tls or qemu+tcp when a username/password using SASL has been
defined on the hypervisor)
Hi John,
The follo
Hi,
Can anyone please share sample Python code for using qemu+tcp with SASL or
qemu+tls with SASL? (i.e., connecting to a hypervisor using qemu+tls or
qemu+tcp when a username/password using SASL has been defined on the hypervisor)
I am having some trouble figuring out how to use callbacks for
