The current state of the ssh transport involves starting the ssh client
process
(command ssh) that communicates using pipes and a socked with the
libvirt client.
Thereafter it behaves as a standard virNetSocket. This configuration has
some
drawbacks, but changing the ssh transport to libssh2
Hi Peter,
Disadvantages:
- break configurations for users that use advanced ssh
configurations in the ssh client
config file
Whenever I had a look at native ssh libraries in Perl or Python I
found GSSAPIAuthentication was not supported.
My favorite ist solution one, a new transport option
On Tue, Oct 18, 2011 at 11:29:46AM +0200, Peter Krempa wrote:
The current state of the ssh transport involves starting the ssh
client process
(command ssh) that communicates using pipes and a socked with the
libvirt client.
Thereafter it behaves as a standard virNetSocket. This configuration
