[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded pam 0.72-18 (m68k) to erlangen



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.7
Date: Sun, 25 Mar 2001 21:40:32 -0500
Source: pam
Binary: libpam-runtime libpam-modules libpam-cracklib libpam0g-dev libpam-doc libpam0g
Architecture: m68k
Version: 0.72-18
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@q650.biophys.uni-duesseldorf.de>
Changed-By: Ben Collins <bcollins@debian.org>
Description: 
 libpam-cracklib - PAM module to enable cracklib support.
 libpam-modules - Pluggable Authentication Modules for PAM
 libpam-runtime - Runtime support for the PAM library
 libpam0g   - Pluggable Authentication Modules library
 libpam0g-dev - Development files for PAM
Closes: 84428 88794 88825 89322 89390
Changes: 
 pam (0.72-18) unstable; urgency=low
 .
   * pam_securetty: log failed tty checks. Normally this was only done if
     the "debug" option was on...do it regardless now, closes: #89390
   * Get rid of log message for when "root" is not applied to group checks.
     closes: #88825
   * Add quiet option to pam_listfile, closes: #84428
   * pam(8) should be pam(7), pam.conf(8) should be pam.conf(5), closes:
     #89322
   * Added groff to Build-Depends-Indep, closes: #88794
Files: 
 157e447ad5a80572dd8fd29fd3407be2 61734 base required libpam0g_0.72-18_m68k.deb
 7866a4669e10160c0439ad29828ccfa7 135754 base required libpam-modules_0.72-18_m68k.deb
 2ef98151568fa5aefbf33f2b9d484298 40544 base required libpam-runtime_0.72-18_m68k.deb
 031ce37e761b3395d167e6722bf76c1b 148092 devel optional libpam0g-dev_0.72-18_m68k.deb
 90d52a0fb507e9455dc7c815f435fba2 42230 libs optional libpam-cracklib_0.72-18_m68k.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQCVAwUBOstmOW547I3m3eHJAQFBCQP/VHu0o9uwiimcHt3QZbc69dmwnY9zbmpp
RZunbtBi1O56NldYbLtufGnQcmF+7GMXFcGYkuf1W0T5oEMteVsbJOoHcZqeK82T
xw0eEz9/1RWvK7BbUjVlWAj+jzf+6xOa1ecZ2JZJusDsoblmk8nsDd+QrGpbpdRA
yWqQRIw/SBI=
=qprn
-----END PGP SIGNATURE-----



Reply to: