Comment 1 for bug 1834128

Thank you for taking the time to report this bug and helping to make Ubuntu better.

It sounds like the actual bug you're reporting is:

> When this happens, other sshd services will fault since the privileged separation directory is no longer there.

Please could you provide exact steps to reproduce your "will fault" prediction? Once done, please change the bug status back to New. I'd appreciate the usual "steps to reproduce/expected behaviour/actual behaviour" clearly laid out please.

As this is an unusual end-user configuration, I'm marking Importance: Low based on our definitions at https://wiki.ubuntu.com/Bugs/Importance. Please note that this means that after you do reply and assuming that we do agree that the actual behaviour is a bug, I expect that a bug report to Debian will be required but no further action will take place in Ubuntu, save for the possibility of patches to stable releases if a fix does land in the development release via Debian and the patch meets our stable update requirements. I expect that if the fix is to sshd@.service then a local workaround will be trivially possible by overriding that service definition.