[Bug 1832110] Re: Resource Sharing with multiple sshd services
Robie Basak
1832110 at bugs.launchpad.net
Wed Jun 12 11:28:30 UTC 2019
Thank you for the additional information.
> The original OpenSSH 7.6p1 source code assigns the privilege
separation directory to /var/empty (see OpenSSH man sshd page).
Does that somehow mean that your problem doesn't occur if you use only
the upstream source code and no distribution patches? If so, how?
> The frustration I have with both the OpenSSH teams and the Ubuntu
teams is neither want to take ownership. I am trying to provide a
solution to both teams and I am getting complete rejection.
Nobody owes you any duty to take ownership. Developers usually care
about issues proportionately to how widely they affect users. I
understand the problem you're facing, but right now it seems to affect
only you, and so I don't think it warrants "taking ownership" by any
team. I don't see this happening unless someone is persuaded on
technical merits such as applicability to a wider use case or a lower
maintenance burden to carry a patch.
Separately from that, if someone offers a patch, as you are doing, then
we are grateful and we will, as a project, make a decision as to whether
it will take it, decline it or require the issue to be resolved in a
different way before accepting it.
> So how can we come to consensus on this?
The consensus amongst Ubuntu developers is currently "Won't Fix" for the
reasons I've given already. As I said, you're welcome to continue
discussion on the technical issues, but on the social side you do seem
have a mistaken expectation that "Won't Fix" somehow means that some
Ubuntu developer is going to "take ownership".
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1832110
Title:
Resource Sharing with multiple sshd services
Status in openssh package in Ubuntu:
Won't Fix
Bug description:
Ubuntu: 18.04.2 LTS
OpenSSH: 7.6p1
I am having a problem starting multiple sshd processes. The default
location of the sshd privilege separation directory is hard-coded to
/run/sshd (see man page). If I want to have 2 sshd services using
systemd, I need to write 2 service files, let's call them
sshd_wan.service ans sshd_lan.service. Both of these services need to
have their own "RuntimeDirectory=sshd_wan" and
"RuntimeDirectory=sshd_lan". If you do not have separate
RuntimeDirectory definitions for the 2 services, then when one service
is killed/faults/restarts/stops/etc. the systemd (or init) process
deletes the RuntimeDirectory and causes the other service to crash
since a RuntimeDirectory does not exist.
The problem is the hard-coding of the sshd Privilege Separation
Directory. We need to modify the OpenBSD/OpenSSH sshd code to
provision command line assignment of the privilege separation
directory.
I have attempted to contact the OpenSSH team (i.e. OpenSSH.com) and
they say it is a Ubuntu problem. I reported this in Ubuntu bug
#1831765 and Ubuntu (e.g. Paride Legovini, June 6, 2019 @ 2:55AM PDT)
rejected it because I described the problem using the init.d example.
I know how to modify the sshd.c file in OpenSSH 7.6p1, the problem is
getting Ubuntu and OpenSSH to admit there is a problem and it needs to
be fixed.
The problem is still there regardless if you are using Upstart (i.e.
init.d) or systemd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1832110/+subscriptions
More information about the foundations-bugs
mailing list