*** This bug is a duplicate of bug 1991592 ***
https://bugs.launchpad.net/bugs/1991592
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu7
---
openssh (1:9.0p1-1ubuntu7) kinetic; urgency=medium
* Update list of stock sshd_config checksums to include those from
*** This bug is a duplicate of bug 1991592 ***
https://bugs.launchpad.net/bugs/1991592
** This bug has been marked a duplicate of bug 1991592
openssh-server should ship a systemd generator to generate ssh socket port
configuration from sshd_config
--
You received this bug notification
I don't have a complete solution to this, but I do have several points.
- debconf prompts on upgrade are not, in general, good UX. It disrupts
the flow of the upgrade. Sometimes it's necessary, but if all it's
doing is telling the user they *may* have a broken config after
upgrading, well, if
** Tags added: ssh-socket-activation
--
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/1990863
Title:
conversion from sshd service to socket is too bumpy
Status in openssh
> what happens in terms of the migration from ssh service to socket when
the user opts to install the vendor version of sshd_config as a result
of the merge conflict
I upgraded today 2022-09-29 and installing the vendor version is not
intended to break the port settings because there's a
Two ideas, one of which I've already mentioned above:
1) You could migrate the address and port settings from sshd_config to
listen.conf _before_ installing the new sshd_config, so that they will
be preserved even if the config gets replaced with the vendor version
because of a merge conflict
On Wed, Sep 28, 2022 at 01:19:35PM -, Jonathan Kamens wrote:
> 1) Nobody reads the release notes.
That's where we document edge case issues that can't be handled
automatically. Maybe we can handle this automatically, which is why I
invited Steve to take a look. But if it turns out that we
1) Nobody reads the release notes.
2) I am not "overwriting configuration files with 'known good' ones," I
am making specific changes to the config files with ansible plays.
Specifically, before fixing my playbook for Kinetic, it looked like
this:
- name: enable root ssh public key
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Feedback on this is appreciated as we do want to make the
transition as smooth as possible.
I would warn though that just overwriting configuration files with
"known good" ones following a release upgrade, as
Hello,
I am unclear about why you are asking for the contents of my sshd_config
file, given that the problem I described here isn't the merge conflict,
but rather what happens in terms of the migration from ssh service to
socket when the user opts to install the vendor version of sshd_config
as a
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
Most relevant information can be found in the discourse post you
mentioned. Could you please share your customization of the
configuration file? So we can understand better the upgrade path you are
going through.
I
11 matches
Mail list logo
