libvirt/tests/qemunbdkitdata/disk-network-ssh-key.args.disk0-src0

SSH_AUTH_SOCK=/path/to/agent/socket \
nbdkit \
--unix /tmp/domain-QEMUGuest1/nbdkit-disk0-src0.socket \
--foreground ssh \
host=example.org \
port=2222 \
path=test1.img \
user=myuser \
known-hosts=/path/to/ssh_known_hosts1
qemu: implement ssh-agent auth for ssh disks with nbdkit It's not possible to use password-protected ssh keys directly with libvirt because libvirt doesn't have any way to prompt a user for the password. To accomodate password-protected key files, an administrator can add these keys to an ssh agent and then configure the domain with the path to the ssh-agent socket. Note that this requires an administrator or management app to configure the ssh-agent with an appropriate socket path and add the necessary keys to it. In addition, it does not currently work with selinux enabled. The ssh-agent socket would need a label that libvirt would be allowed to access rather than unconfined_t. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> 2023-07-14 20:54:03 +00:00			`SSH_AUTH_SOCK=/path/to/agent/socket \`
qemu: implement keyfile auth for ssh disks with nbdkit For ssh disks that are served by nbdkit, we can support logging in with an ssh key file. Pass the path to the configured key file and the username to the nbdkit process. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> 2022-12-22 22:56:47 +00:00			`nbdkit \`
qemu: fix nbdkit command test for backing chains Previously this test only tested the generated nbdkit command for the top level disk source. Update it to test the generated commmands for all sources in the chain. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> 2024-01-26 16:41:58 +00:00			`--unix /tmp/domain-QEMUGuest1/nbdkit-disk0-src0.socket \`
qemu: implement keyfile auth for ssh disks with nbdkit For ssh disks that are served by nbdkit, we can support logging in with an ssh key file. Pass the path to the configured key file and the username to the nbdkit process. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> 2022-12-22 22:56:47 +00:00			`--foreground ssh \`
			`host=example.org \`
			`port=2222 \`
qemu: implement ssh-agent auth for ssh disks with nbdkit It's not possible to use password-protected ssh keys directly with libvirt because libvirt doesn't have any way to prompt a user for the password. To accomodate password-protected key files, an administrator can add these keys to an ssh agent and then configure the domain with the path to the ssh-agent socket. Note that this requires an administrator or management app to configure the ssh-agent with an appropriate socket path and add the necessary keys to it. In addition, it does not currently work with selinux enabled. The ssh-agent socket would need a label that libvirt would be allowed to access rather than unconfined_t. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> 2023-07-14 20:54:03 +00:00			`path=test1.img \`
qemu: implement keyfile auth for ssh disks with nbdkit For ssh disks that are served by nbdkit, we can support logging in with an ssh key file. Pass the path to the configured key file and the username to the nbdkit process. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> 2022-12-22 22:56:47 +00:00			`user=myuser \`
qemu: implement ssh-agent auth for ssh disks with nbdkit It's not possible to use password-protected ssh keys directly with libvirt because libvirt doesn't have any way to prompt a user for the password. To accomodate password-protected key files, an administrator can add these keys to an ssh agent and then configure the domain with the path to the ssh-agent socket. Note that this requires an administrator or management app to configure the ssh-agent with an appropriate socket path and add the necessary keys to it. In addition, it does not currently work with selinux enabled. The ssh-agent socket would need a label that libvirt would be allowed to access rather than unconfined_t. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> 2023-07-14 20:54:03 +00:00			`known-hosts=/path/to/ssh_known_hosts1`