Description of problem:

A libvirt client (ie virsh) built without support for PolicyKit isn't able to connect to a libvirt daemon that *is* using PolicyKit, over SSH.

(The same client can authenticate using TLS though.)

For example, if a client is built using "--without-polkit" on Linux, or is built on an OS with PolicyKit (Mac OS X), connecting over SSH will give:

  $ virsh -d 5 -c 'qemu+ssh://username@hostname/system'
  error: authentication failed: unsupported authentication type 2
  error: failed to connect to the hypervisor
  $

This failure message is returned _after_ the SSH layer has been successfully established, when netcat connects to the socket file.

The libvirt daemon receives the connection, but immediately drops it. (unsure why at this stage)

*THIS IS THE BUG*

Even though PolicyKit wasn't compiled into the libvirt client, PolicyKit on the server is what's responsible for the auth checking, and it successfully does this.  The libvirt daemon shouldn't then drop the connection after the client has auth'd ok.


Version-Release number of selected component (if applicable):

Present git head of libvirt.  0.8.4+


How reproducible:

Every time.


Steps to Reproduce:
1. Build virsh using "--without-polkit" on the ./configure line
2. Use it to connect to a RHEL6 or Fedora 13 box that has PolicyKit enabled (it is by default)
3. Even if the user has sufficient authorisation, the libvirt daemon drops the connection.  This is the bug.

  
Actual results:

  The libvirt daemon drops the connection.


Expected results:

  The libvirt client should be able to use the established connection.  It has, after all, already authenticated ok.


Additional info:

  Possibly the only workaround for Mac OS X clients for now, until this is fixed, is to disable PolicyKit usage by libvirt on the server side.  Open to other suggestions. :)