Re: [Spice-devel] progress on virt-viewer for windows

2013-09-19 Thread Fernando Lozano
Hi, My first tests using virsh from http://teuf.fedorapeople.org/virt-viewer-msi/ were based on the 64-bit (x86_64) binaries. I'll try the 32-bit binaries and report on the results. The 32-bit binaries needed the same DLLs (of course the 32-bit ones) and gave the same results: virsh works with

Re: [Spice-devel] progress on virt-viewer for windows

2013-09-19 Thread Fernando Lozano
Hi Marc, C:\Program Files\VirtViewer\bin>virsh -c qemu+tcp://kvmhost/system error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 1 It looks like the windows port can't do SASL auth over TCP. So I changed libvirtd.conf to allow unauthenticated c

Re: [Spice-devel] progress on virt-viewer for windows

2013-09-19 Thread Fernando Lozano
Hi, My first tests using virsh from http://teuf.fedorapeople.org/virt-viewer-msi/ were based on the 64-bit (x86_64) binaries. I'll try the 32-bit binaries and report on the results. After having success with a few comands using virsh, I decided to try virt-viewer. It reported missing libss

[Spice-devel] progress on virt-viewer for windows

2013-09-19 Thread Fernando Lozano
Hi Christophe, If someone provides newer windows binaries -- which aren't missing dlls, like the ones at http://teuf.fedorapeople.org/virt-viewer-msi/ -- I will test then. I gave you links to RPMs containing the missing dlls (rpm2cpio foo.dll | cpio -id will unpack them on linux) in https://ww

Re: [Spice-devel] progress on virt-viewer for windows

2013-09-19 Thread Marc-André Lureau
- Original Message - > Hi Christophe, > >> If someone provides newer windows binaries -- which aren't missing > >> dlls, like the ones at http://teuf.fedorapeople.org/virt-viewer-msi/ > >> -- I will test then. > > I gave you links to RPMs containing the missing dlls (rpm2cpio foo.dll > >

[Spice-devel] [spice-gtk PATCHv3 2/2] Use system-wide trust certificate store

2013-09-19 Thread Christophe Fergeau
Currently, spice-gtk will look in $HOME/.spicec/spice_truststore.pem by default for its trust certificate store (to verify the certificates used during SPICE TLS connections). However, these days a system-wide trust store can be found in /etc/pki or /etc/ssl. This commit checks at compile time wher

[Spice-devel] [spice-gtk PATCHv3 1/2] Add SpiceSession:use-system-ca-file property

2013-09-19 Thread Christophe Fergeau
This property indicates whether to look into the system CA database when validating certificates in a TLS connection. This property defaults to TRUE, but is automatically set to FALSE when SpiceSession:ca-file is set. --- gtk/spice-option.c | 8 gtk/spice-session-priv.h | 3 +++ g

[Spice-devel] [spice-gtk PATCHv3 0/2] Use system CA store

2013-09-19 Thread Christophe Fergeau
Hey, Here is the v2 of my patch series adding a way for spice-gtk to look into the system CA store when it validates a TLS certificate. There is now a SpiceSession::use-system-ca-file property to let library user enable/disable it as they want. The default behaviour is that it's enabled unless so