libvirt/30-libvirt-ssh-proxy.conf.in at dd085b1a16589b7c7f8d9884baea221f74ba689c - libvirt - Gitea

External/libvirt

mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-09 23:10:08 +00:00

Michal Privoznik 0287b5dfd2 tools: Introduce SSH proxy

This allows users to SSH into a domain with a VSOCK device:

  ssh user@qemu/machineName

So far, only QEMU domains are supported AND qemu:///system is
looked for the first for 'machineName' followed by
qemu:///session. I took an inspiration from Systemd's ssh proxy
[1] [2].

To just work out of the box, it requires (yet unreleased) systemd
to be running inside the guest to set up a socket activated SSHD
on the VSOCK. Alternatively, users can set up the socket
activation themselves, or just run a socat that'll forward vsock
<-> TCP communication.

1: https://github.com/systemd/systemd/blob/main/src/ssh-generator/ssh-proxy.c
2: https://github.com/systemd/systemd/blob/main/src/ssh-generator/20-systemd-ssh-proxy.conf.in

Resolves: https://gitlab.com/libvirt/libvirt/-/issues/579
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>

2024-05-13 08:56:35 +02:00

7 lines

183 B

Plaintext

Raw Blame History

 # SPDX-License-Identifier: LGPL-2.1-or-later
 Host qemu/* qemu:system/* qemu:session/*
     ProxyCommand @libexecdir@/libvirt-ssh-proxy %h %p
     ProxyUseFdpass yes
     CheckHostIP no