This bug was fixed in the package openssh - 1:8.2p1-4ubuntu0.3
---
openssh (1:8.2p1-4ubuntu0.3) focal; urgency=medium
* d/systemd/ssh@.service: preserve the systemd managed runtime directory to
ensure parallel processes will not disrupt one another when halting
(LP:
This bug was fixed in the package openssh - 1:8.4p1-5ubuntu1.1
---
openssh (1:8.4p1-5ubuntu1.1) hirsute; urgency=medium
* d/systemd/ssh@.service: preserve the systemd managed runtime directory to
ensure parallel processes will not disrupt one another when halting
(LP:
I verified the fixes by following the steps in the test plan described
above by using the attached script on both focal and hirsute LXC
containers.
The tests show that the patch successfully fixes the described issue.
** Attachment added: "reproduce.sh"
Hello Marcin, or anyone else affected,
Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Marcin, or anyone else affected,
Accepted openssh into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openssh/1:8.4p1-5ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks, Robie!
I proposed a patch for hirsute which was already uploaded.
** Changed in: openssh (Ubuntu Hirsute)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/openssh/+git/openssh/+merge/406318
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Also affects: openssh (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Hirsute)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The upload looks fine, but do you have any plans to fix Hirsute?
Otherwise users upgrading from Focal up to Hirsute will be regressed
after this fix is landed. It should be trivial to also fix this in
Hirsute I think - and might even be beneficial to do first as a canary.
** Description changed:
** Changed in: openssh (Ubuntu Focal)
Status: New => In Progress
--
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/1905285
Title:
socket-activated sshd breaks on
** Merge proposal linked:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/openssh/+git/openssh/+merge/406161
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Description changed:
+ [Impact]
+
+ Users of the systemd socket activated ssh service may experience a race
+ condition that may lead an ssh instance to fail.
+
+ The race condition happens when, for a running socket activated ssh
+ service,
+
+ an instance A is started, creating the
This bug was fixed in the package openssh - 1:8.4p1-5ubuntu2
---
openssh (1:8.4p1-5ubuntu2) impish; urgency=medium
* d/systemd/ssh@.service: preserve the systemd managed runtime directory to
ensure parallel processes will not disrupt one another when halting
(LP: #1905285)
** Merge proposal linked:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/openssh/+git/openssh/+merge/405183
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
I'm seeing something similar to this (messages more like those in
underlying debian bug report) - in this case triggered by a script which
sshs in (invoking unison) twice in quick succession. Underlying hardware
is an ARM board which may a little slow, don't know if that helps to
trigger race?
Thanks for the comment, Marcin. Yes, you're right, the correct file to
edit was ssh@.service indeed. That was a thinko on my part.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Hello Segio,
Have you tried editing ssh@.service as well? In my case, sshd.service ->
ssh.service and that is not used when ssh is in socket-activated mode,
ssh@.service is, at least that's how I understand systemd.
I now understand how to override the unit files with [unit-
Thanks for the report.
I was able to reproduce this bug. Basically:
$ systemctl start ssh.socket
$ ssh-keyscan localhost
Interesting enough, I wasn't able to solve the problem by setting
RuntimeDirectoryPreserve=yes. I edited sshd.service and added the
directive there, but I still see the
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Hello Marcin, the Description section of
https://www.freedesktop.org/software/systemd/man/systemd.unit.html gives
information on how to modify configurations without having them undone
by future updates; the systemctl edit command automates the process of
using these local modifications.
Thanks
20 matches
Mail list logo
