]> code.ossystems Code Review - openembedded-core.git/commit
sudo: handle glibc 2.17 crypt semantics
authorRoss Burton <ross.burton@intel.com>
Thu, 11 Apr 2013 14:57:58 +0000 (15:57 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 11 Apr 2013 15:12:00 +0000 (16:12 +0100)
commit06d7078f7631b92e8b789f8e94a3a346d8181ce6
treed6be0659ffe8819f666fe47088385a56f63d674e
parented03b850daf223ed89f8524e22fb28e259c3286a
sudo: handle glibc 2.17 crypt semantics

Staring from glibc 2.17 the crypt() function will error out and return NULL if
the seed or "correct" is invalid. The failure case for this is the sudo user
having a locked account in /etc/shadow, so their password is "!", which is an
invalid hash.  crypt() never returned NULL previously so this is crashing in
strcmp().

[ YOCTO #4241 ]

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-extended/sudo/files/crypt.patch [new file with mode: 0644]
meta/recipes-extended/sudo/sudo_1.8.6p7.bb