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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832110 Title: Resource Sharing with multiple sshd services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1832110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
