Thanks Robie. I think you may have misunderstood what the bug is. The
quote you reference is not really relevant in this case, because what I
am reporting isn't that something goes wrong when a port is not
specified.
The important line from the documentation is this, which I provided
originally:
"Additionally, any Port options must precede this option for non-port
qualified addresses."
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.
I agree that part of this could legitimately be a bug in OpenSSH.
** Changed in: openssh (Ubuntu)
Status: Invalid => Opinion
** Changed in: openssh (Ubuntu)
Status: Opinion => New
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
