This bug was fixed in the package openssh - 1:9.6p1-3ubuntu13
---
openssh (1:9.6p1-3ubuntu13) noble; urgency=medium
[ Marco Trevisan (Treviño) ]
* debian: Remove dependency on libsystemd
As per the xz backdoor we learned that the least dependencies sshd have,
the best it
** Changed in: openssh (Ubuntu)
Status: Confirmed => Fix Committed
--
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
** Information type changed from Public to Public Security
--
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
> For me the biggest problem was the socket unit beeing re-enabled when
I had it disabled it but still running sshd.service (ie without socket
activation) - now you're unexpectidly switched back to using socket
activation - something I explicitly opted out of.
Okay. We could probably adjust the
I'm not that invested in the having openssh-server installed but not
running use-case, but in general people do not like their local
configuration beeing overridden on package upgrades in this manner.
I could image people having it installed for the man-pages, or maybe
using other units for it
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:
6 matches
Mail list logo
