openssh: avoid checking empty passwords to mess up with PAM modules
authorChen Qi <Qi.Chen@windriver.com>
Wed, 2 Jul 2014 06:24:39 +0000 (14:24 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 3 Jul 2014 16:41:18 +0000 (17:41 +0100)
commit1d79479ec58b71783c5b5fbb5fc8505437979efb
treeb5cef247cc6bfe7db1bc42e705a2647b6239d2b5
parent539676976b953191ad7971a5601f74b36b4b1601
openssh: avoid checking empty passwords to mess up with PAM modules

Previously, even if PAM is enabled for ssh, the daemon still tries to
authenticate an empty password. This leads to authentication failure
which would mess up with PAM modules.

As a result, if 'UsePAM', 'PermitEmptyPasswords' and 'PasswordAuthentication'
are enabled, no user can login correctly. We would meet the following error
message at the client side.

Write failed: Broken Pipe

This patch fixes the above problem by checking whether PAM is enabled before
authenticating an empty password. After all, if PAM is enabled, the task of
authenticating passwords should be handled to PAM modules.

[YOCTO #6466]

(From OE-Core rev: e017ae71dad4837b0d22f291b0b0e0949075f822)

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-connectivity/openssh/openssh/auth2-none.c-avoid-authenticate-empty-passwords-to-m.patch [new file with mode: 0644]
meta/recipes-connectivity/openssh/openssh_6.6p1.bb