Download Latest Version shadow-4.1.5.1-glibc217-crypt.diff (7.5 kB)
Email in envelope

Get an email when there's a new version of mancha's vault

Home / glibc217
Name Modified Size InfoDownloads / Week
Parent folder
SHA256SUMS.sig 2014-06-18 543 Bytes
SHA256SUMS 2014-06-18 1.7 kB
yp-tools-2.14-glibc217-crypt.diff 2014-06-18 2.6 kB
README 2014-02-03 740 Bytes
gdm-2.20.11-glibc217-crypt.diff 2014-01-31 4.3 kB
vm-pop3d-1.1.7f-glibc217.diff 2013-12-26 1.9 kB
xlockmore-5.42-glibc217-crypt.diff 2013-10-17 4.0 kB
xdm-1.1.11-glibc217-crypt.diff 2013-10-17 1.5 kB
tcsh-6.18.01-glibc217-crypt.diff 2013-10-17 696 Bytes
slim-1.3.5-glibc217-crypt.diff 2013-10-17 987 Bytes
shadow-4.1.5.1-glibc217-crypt.diff 2013-10-17 7.5 kB
screen-glibc217-crypt.diff 2013-10-17 3.8 kB
ppp-2.4.5-glibc217-crypt.diff 2013-10-17 2.1 kB
popa3d-1.0.2-glibc217-crypt.diff 2013-10-17 2.0 kB
openswan-2.6.39-glibc217-crypt.diff 2013-10-17 1.2 kB
kde-workspace-4.10.5-glibc217-crypt.diff 2013-10-17 3.7 kB
dropbear-2013.58-glibc217-crypt.diff 2013-10-17 840 Bytes
cyrus-sasl-2.1.26-glibc217-crypt.diff 2013-10-17 3.6 kB
cyrus-sasl-2.1.23-glibc217-crypt.diff 2013-10-17 3.4 kB
cvs-1.11.23-glibc217-crypt.diff 2013-10-17 2.4 kB
Totals: 20 Items   49.4 kB 0
Starting with glibc 2.17 (eglibc 2.17), the crypt() function will
return NULL with EINVAL when supplied a bad salt. Further, in the
case of unsupported salts (i.e. DES and MD5) while in FIPS-140 mode,
crypt() will return NULL with EPERM.

As a result, many programs that rely on glibc's crypt() need to be
patched to account for possible NULL returns and avoid null-pointer
dereferences that in the case of services can result in DoS.

This directory contains a set of patches (most of which I authored)
that fix the handling of the crypt() in glibc 2.17 onwards.

Note: All the patches I've authored have been submitted upstream
      and, with a single exception (yptools developer seems to be
      AWOL), have been mainlined.

--mancha
Source: README, updated 2014-02-03