** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055806
Title:
sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing
privilege separation directory:
This bug was fixed in the package openssh - 1:9.6p1-3ubuntu11
---
openssh (1:9.6p1-3ubuntu11) noble; urgency=medium
* d/t/ssh-gssapi: make the test a bit more rebust (LP: #2058276):
- deal with return codes
- match a more specific success expression from the logs
- add
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055806
Title:
sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing
** Also affects: openssh (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Mantic)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => High
** Tags
I think we originally broke this out into a tmpfile since the openssh-
server.postinst was calling sshd -G to parse config. However, with the
sshd-socket-generator approach, we don't call sshd directly anymore, so
we could probably just go back to setting RuntimeDirectory=/run/sshd in
ssh.service.
** Tags added: rls-nn-incoming
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055806
Title:
sshd.service
I've changed the Unit files for the mount and automount points and will
see if this was the cause of the unit ordering issue. I commented out
the Requires= files and just left the After= files to create a softer
dependency tree.
```
''# cat mnt-xbmc\\x2ddata.mount''
[Unit]
Description=mount
I'm looking at the journalctl logs for systemd-tmpfiles-setup.service
and sysinit.target/start and it shows up that one of the mount and
automount units that I created might have caused a problem and systemd
somehow deleted the start events for systemd-tmpfiles-
setup.service/start event.
This
When the /run/sshd/ directory exits and looks good.
```
'''stat /run/sshd'''
File: /run/sshd
Size: 40 Blocks: 0 IO Block: 4096 directory
Device: 0,25Inode: 1786Links: 2
Access: (0755/drwxr-xr-x) Uid: (0/root) Gid: (0/root)
Access:
More discussion threads regarding this issue.
This is an old one from 16.04 before ssh socket activation.
https://askubuntu.com/questions/1110828/ssh-failed-to-start-missing-
privilege-separation-directory-var-run-sshd
Another older report from 5-years ago from 16.04.05 again.
Found this reference also to this folder.
```
''man sshd''
/run/sshd
chroot(2) directory used by sshd during privilege separation in
the pre‐authentication phase. The directory should not contain any files and
must be owned by root and not group or world‐writable.
```
--
You
** Tags added: packaging systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055806
Title:
sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing
privilege separation directory:
This is a follow-up to the problems reported in the following thread
that already discussed an issue with socket activation for the
ssh.service.
SSHd now uses socket-based activation (Ubuntu 22.10 and later)
13 matches
Mail list logo
