I have not tested this, but can't this just be addressed by the
following?
$ mkdir -p /etc/systemd/system/ssh.socket.d/
$ cat > /etc/systemd/system/ssh.socket.d/vsock.conf << EOF
[Socket]
ListenStream=<your vsock config>
EOF
That will give you ssh.socket which listens on vsock, *in addition* to
whatever other sshd config is in place (you could completely override
instead if you wanted).
The way the default ssh.socket and ssh.service are setup, it will
happily listen on multiple ports/sockets/addresses whatever. The sshd-
socket-generator writes its config in /run/systemd/generator, which
means the admin can still append/override the socket configuration with
files in /etc/systemd/system.
It seems to me that if you are modifying the socket unit to make this
work anyways, that just adding a drop-in configuration is preferable. Or
am I missing something about the integration here?
** Changed in: openssh (Ubuntu Noble)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111226
Title:
[email protected] is still needed for hv_sock in Noble release
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2111226/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
