> So, yes, my configuration is invalid, but the behavior of sshd when
this happens and the experience around it could use improvement. If it
detects that the configuration is invalid, it should flag it as such and
make it obvious from the logs/stdout/stdterr rather than letting the
process try to restart and falsely report that it restarted
successfully, because it didn't.
This seems reasonable, but as you point out it would be something that
would need to be done upstream. I don't think it's appropriate for
Ubuntu to deviate from upstream on this behaviour.
To set expectations I'll set this bug Won't Fix for Ubuntu, as I don't
think we'd accept patches for this. But if upstream make related
changes, we could change the bug status to track the availability of
those changes in Ubuntu at that point.
** Changed in: openssh (Ubuntu)
Status: New => Won't Fix
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521745
Title:
sshd will fail to start or restart if non-default Port option is
incorrectly put after a non-default ListenAddress
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1521745/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
