Is there a strong use case for installing openssh-server, but then not
wanting it to run as a daemon (i.e. disabling the necessary systemd
units)? The purpose of this snippet is to migrate to socket activated
sshd by default, which is the case for new installs of openssh-server.
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2059874
Title:
on upgrade sshd-socket-generator conversion does not respect
administrator intent
Status in openssh package in Ubuntu:
Incomplete
Bug description:
the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code
snippet:
if [ "$action" == configure ]; then
..snip..
if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then
..snip..
if [ -d /run/systemd/system ]; then
# Make sure ssh.service is disabled.
systemctl unmask ssh.service
systemctl disable --now ssh.service > /dev/null 2>&1
# sshd-socket-generator is invoked on daemon-reload.
systemctl daemon-reload
systemctl enable ssh.socket
fi
fi
fi
This does not respect existing service and socket unit configuration,
it effectively re-enables a disabled ssh.service (and even a masked
one), and a manually disabled socket unit. I strongly suspect it does
not respect systemd presets either.
This is unexpected behaviour.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
