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

Uploaded pam 0.72-9 (m68k) to erlangen



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.6
Date: Wed, 14 Jun 2000 11:38:35 -0400
Source: pam
Binary: libpam-cracklib libpam0g-dbg libpam-runtime libpam-pwdb libpam-doc libpam0g-dev libpam-modules libpam0g
Architecture: m68k
Version: 0.72-9
Distribution: frozen unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
Description: 
 libpam-cracklib - PAM module to enable cracklib support.
 libpam-modules - Pluggable Authentication Modules for PAM
 libpam-pwdb - PAM module to enable libpwdb (Password Database) support.
 libpam-runtime - Runtime support for the PAM library
 libpam0g   - Pluggable Authentication Modules library
 libpam0g-dbg - Static library with debugging symbols for libpam
 libpam0g-dev - Development files for PAM
Closes: 65321 65401
Changes: 
 pam (0.72-9) frozen unstable; urgency=low
 .
   * pam_unix: do not call obscure_msg() of pass_old is NULL,
     closes: #65321
   * pam_access: check for from[0] == '\0' so that tty logic is actually
     used, closes: #65401
Files: 
 251f64f76e4c17bdec56ccc7f74392d6 57806 base required libpam0g_0.72-9_m68k.deb
 4274e72ec2324001cfbb1d5925f28528 132576 base required libpam-modules_0.72-9_m68k.deb
 37ee034c9addea13b26ee1d5257ddead 39732 base required libpam-runtime_0.72-9_m68k.deb
 716bacf5ef5d180647b6adc98f1ab27e 164050 devel optional libpam0g-dev_0.72-9_m68k.deb
 b002cf6e514a7433e2bb3da294c6fd8d 252624 devel extra libpam0g-dbg_0.72-9_m68k.deb
 f3b205543866a85b6a2c9256ef73f4e8 39472 admin optional libpam-cracklib_0.72-9_m68k.deb
 c8f07e46b690bf1c1a46d6dffdaa2cad 53072 admin optional libpam-pwdb_0.72-9_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (SunOS)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iEYEARECAAYFAjlXEzwACgkQcS3JWD3FdvcNKgCfa3rP3nLXBQpNL+Ys3AQ9/jdv
fNMAnR4XzdZgYGXJQhqHHx73naG5H/fl
=OK7U
-----END PGP SIGNATURE-----



Reply to: