[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2016-10-25 Thread Robie Basak
> 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 r

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-14 Thread jhartr7
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:

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-14 Thread Robie Basak
Thank you for the update. On looking again I noticed this from the documentation you quoted in your original report: "If port is not specified, sshd will listen on the address and all prior Port options specified." I'm sorry I didn't notice this the first time round. Given the word "prior" in th

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-11 Thread jhartr7
I've attached my mostly default configuration that does not exhibit the problem as well as the configuration that does exhibit the problem. Obviously, to reproduce this you'll need to use a ListenAddress and perhaps a Port argument that suits your setup. To reproduce this, take my original configu

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-11 Thread jhartr7
Here is the default configuration file I had been using prior to modifications. AFAIK it is nearly identical to the default that comes with whatever version of OpenSSH that ships with 12.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-11 Thread jhartr7
** Attachment added: "default pre-bug sshd_config" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1521745/+attachment/4533350/+files/sshd_config -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. ht

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-11 Thread jhartr7
** Attachment added: "modified sshd_config exhibiting bug" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1521745/+attachment/4533351/+files/sshd_config -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ub

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-04 Thread Robie Basak
(ideally this would be the minimal change from the default configuration, to make it easiest to identify the cause of the problem) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/b

[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2015-12-04 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please attach an example sshd_config that fails as you describe, and then change the bug status back to New. Thanks! ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug noti