[libvirt PATCH 0/9] remote: introduce a custom netcat impl for ssh tunnelling

We have long had a problem with use of netcat for ssh tunnelling because there's no guarantee the UNIX socket path the client builds will match the UNIX socket path the remote host uses. We don't even allow session mode SSH tunnelling for this reason. We also can't easily auto-spawn libvirtd in ses

Re: [libvirt PATCH 0/9] remote: introduce a custom netcat impl for ssh tunnelling

On 7/9/20 8:36 PM, Daniel P. Berrangé wrote: We have long had a problem with use of netcat for ssh tunnelling because there's no guarantee the UNIX socket path the client builds will match the UNIX socket path the remote host uses. We don't even allow session mode SSH tunnelling for this reason.