Re: [Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-14 Thread Robie Basak
You're going round in circles. Let's take a step back. Please assume that Ubuntu does not want to make any change right now because no change is currently considered justified. An open question here is if Ubuntu's patches on upstream are creating any problem that you're reporting. That's why I'm

Re: [Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-14 Thread Robie Basak
On Fri, Jun 14, 2019 at 04:02:10PM -, Luke A. Perkins wrote: > When I compile this version of the code, the privilege > separation directory is defined as "/var/empty" which would solve the > problem. Why/how would this solve the problem? > So, which git repository should I use to

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-14 Thread Luke A. Perkins
My recommmendation moving forward. 1) If Ubuntu wants to move the privilege separation directory from /var/empty to /run/sshd, then there needs to be a command-line option for the sshd to adjust the location of the privilege separation directory. 2) If Ubuntu keeps the privilege separation

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-14 Thread Luke A. Perkins
This is the git diff of sshd.c ** Patch added: "sshd.c.diff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1832110/+attachment/5270821/+files/sshd.c.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-14 Thread Luke A. Perkins
This is a proposed patch of "disco-proposed" of the sshd.c file. I have uploaded the original and the diff version. ** Attachment added: "The proposed changed sshd.c file in its entirety." https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1832110/+attachment/5270820/+files/sshd.c --

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-14 Thread Luke A. Perkins
> 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? Good question. I have cloned the git version of OpenSSH for disco- proposed. When I compile this version of the code, the privilege separation directory is

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-12 Thread Robie Basak
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

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-11 Thread Luke A. Perkins
Robie, There are several options moving forward: 1) We need the /run/sshd file (see Ubuntu's man sshd page) to be configurable. The problem with locating the privilege separation directory in a fixed location, the systemd does not do well in multiple sshd instance assignments. The systemd will

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-11 Thread Robie Basak
> If I upload the sshd.c proposed change, will that be possibility? Please do attach the diff for reference - that is useful for the record. I think it will still be unlikely though. Introducing new configuration options in a distribution delta is particularly painful because if upstream later

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-10 Thread Luke A. Perkins
Robbie, If I upload the sshd.c proposed change, will that be possibility? I have diffed the sshd.c code against the OpenSSH 7.6p1 source. Ubuntu has made significant and substantial changes to all of the OpenSSH source. So I know Ubuntu does not use the original OpenSSH code verbatim. Is there

[Bug 1832110] Re: Resource Sharing with multiple sshd services

2019-06-10 Thread Robie Basak
Thank you for taking the time to file this bug and helping to make Ubuntu better. > ...the problem is getting Ubuntu and OpenSSH to admit there is a problem and it needs to be fixed. It's up to individual projects to decide what configurations they want to support. Just because you can't