Uploaded shadow 20000902-2 (m68k) to erlangen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 31 Dec 2000 14:33:47 -0500
Source: shadow
Binary: passwd login
Architecture: m68k
Version: 20000902-2
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
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:
95ebab7454b64d8f80098f0e18b58e3f 254096 base required passwd_20000902-2_m68k.deb
fe3a439ebfb35e3d8a3c15196b740d19 108190 base required login_20000902-2_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>
iEYEARECAAYFAjpUQKgACgkQcS3JWD3FdvcW5ACfZ18naFpYEPWilBnAqN3Bx6me
rcwAnRIYH+HMLZMFH8jSZC0hsIYm8n/i
=M1ho
-----END PGP SIGNATURE-----
Reply to: