[Bug 1656557] Re: sshd_config issue crashes sshd daemon

Colin Watson cjwatson at canonical.com
Sun Jan 15 01:15:16 UTC 2017


This is true of all the purely yes/no flags; I agree that there are some
multi-state options that behave differently.

I've raised this upstream, and linked the bug here.  Thanks for your
report.  I should warn you in advance that a backport to 14.04/16.04 is
rather unlikely, but if fixed upstream then it'll make its way into
later Ubuntu releases.

** Bug watch added: OpenSSH Portable Bugzilla #2664
   https://bugzilla.mindrot.org/show_bug.cgi?id=2664

** Also affects: openssh via
   https://bugzilla.mindrot.org/show_bug.cgi?id=2664
   Importance: Unknown
       Status: Unknown

** Summary changed:

- sshd_config issue crashes sshd daemon
+ sshd boolean option parsing is excessively case-sensitive

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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



More information about the foundations-bugs mailing list