Hi Collin, thanks for the input. I've spoken to upstream also about this, and they informed me that some options are parsed with a more advanced parser than others (the last being yes/no).
Their advice was to follow the comments spec. -- 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/1656557 Title: sshd boolean option parsing is excessively case-sensitive Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: Dear People, The field 'PasswordAuthentication' unlike all the others requires no capitalization in order for the ssh daemon to start properly! While this works: PasswordAuthentication yes The following doesn't work for this field (though works for other fields): PasswordAuthentication Yes This is most likely an issue to bring up to upstream project. Could we have a fix so that configuration can be done in a consistent way and the daemon doesn't break because of capitalization of a given parameter (it works on the other fields using [Yy] or [Nn]). This is a reality in 14.04 and 16.04. Thanks for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1656557/+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
