Public bug reported:
OpenSSH 7.9p1
Ubuntu 18..04.2 (LTS)
If a sshd daemon is started with a "-f my_sshd_config" command-line
specification the sshd process still requires the existence of the
sshd_config. The bug is somewhere in one of the forked processes started
when an external client attempts a connection. Since the sshd_config
file does not exists, an external client connection cannot be started.
Solution: If I "touch /etc/ssh/sshd_config" then the lock-up issue goes
away and I am successfully able to login.
Bug: If the sshd configuration file is specified in the command line
execution of the daeomon, then this should be the only file that should
be required.
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
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/bugs/1834129
Title:
Presence of sshd_config mandatory
Status in openssh package in Ubuntu:
New
Bug description:
OpenSSH 7.9p1
Ubuntu 18..04.2 (LTS)
If a sshd daemon is started with a "-f my_sshd_config" command-line
specification the sshd process still requires the existence of the
sshd_config. The bug is somewhere in one of the forked processes
started when an external client attempts a connection. Since the
sshd_config file does not exists, an external client connection cannot
be started.
Solution: If I "touch /etc/ssh/sshd_config" then the lock-up issue
goes away and I am successfully able to login.
Bug: If the sshd configuration file is specified in the command line
execution of the daeomon, then this should be the only file that
should be required.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834129/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
