Installed shadow 20000902-2 (sparc source)

[Ben Collins <bcollins@debian.org>]

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

Format: 1.7
Date: Sun, 31 Dec 2000 14:33:47 -0500
Source: shadow
Binary: login passwd
Architecture: source sparc
Version: 20000902-2
Distribution: unstable frozen
Urgency: low
Maintainer: Ben Collins <bcollins@debian.org>
Changed-By: Ben Collins <bcollins@debian.org>
Description: 
 login      - System login tools
 passwd     - Change and administer password and group data.
Closes: 17911 63801 64756 71114 75435 75510 76806 76817 76898 77824 77940 78186 79447 80111 80398 80494
Changes: 
 shadow (20000902-2) unstable frozen; urgency=low
 .
   * control.hurd->control.gnu: closes: #77940
   * Cannot reproduce, closes: #79447
   * User never sent a patch, plus I think removing the passwd/account when
     doing passwd -l is a bad idea. Makes it so you cannot unlock the
     account. closes: #77824
   * Don't allow shadowconfig to change perms of other binaries, close: #77057
   * IMO, this is not a bug. It's part of a feature, and can be disabled by
     turning off USER_GROUPS. closes: #76806
   * /bin/login is suid root for several good reasons. For one, it allows
     daemons that use it to run as non-root. This is a good thing since it
     means only one program is running as root, and not several. closes: #17911
   * sulog is fairly easy to grep or parse so I don't see how the
     similarity of the log entries for failed and successful is a problem.
     '-' for failed, '+' for success. closes: #63801
   * logoutd.8: s,/etc/utmp,/var/run/utmp, closes: #80494
   * Fix case where pam_auth returns a NULL username, closes: #76817, #75510
   * Hmm, Linux is a sysv derivative, so the comment is perfectly
     legitimate, closes: #76898
   * MAX_PASSWORD is used by useradd, and CHFN_AUTH is actually used by
   * chfn to decide if the current user needs to auth in order to change
     their info, closes: #71114
   * login.1: Fix \' closes: #75435
   * login -f works for me assuming you call it as root. I tested this with
     plain pam_unix.so, and also with pam_unix.so stacked with pam_ldap.so.
     So if it doesn't work with telnet-heimdal, then that program is not
     doing something right. closes: #78186
   * login.pam.d: made pam_nologin.so requisite. closes: #80111
   * su to root seems pretty quick to me, closes: #64756
   * xmalloc.c: remove decleration of malloc, which was causing system
   * header conflicts. closes: #80398
Files: 
 d977c7eeb9541d3a265bac7f88d89d16 656 base required shadow_20000902-2.dsc
 728cc26cfef800f67469f0acdda57459 44557 base required shadow_20000902-2.diff.gz
 3edf1accdf0449dc40a71c83746e6e04 289840 base required passwd_20000902-2_sparc.deb
 2e3a7199567595cf6b140b27b4717be4 116632 base required login_20000902-2_sparc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins <bcollins@debian.org>

iD8DBQE6T4xQfNc/ZB4E7C0RAv5OAKCxS/JtDP6GEqSH2eGrxHkPt89eewCfezJU
lhG2daVZr7AsLRRphXJw7BE=
=w1IQ
-----END PGP SIGNATURE-----


Installed:
shadow_20000902-2.dsc
  to pool/main/s/shadow/shadow_20000902-2.dsc
login_20000902-2_sparc.deb
  to pool/main/s/shadow/login_20000902-2_sparc.deb
passwd_20000902-2_sparc.deb
  to pool/main/s/shadow/passwd_20000902-2_sparc.deb
shadow_20000902-2.diff.gz
  to pool/main/s/shadow/shadow_20000902-2.diff.gz