conversion to shadowed passwords was easy enough on 4.2, now how about
*double-length* passwords? or do i have to get the source for the
shadow suite and install it?
--
conversion to shadowed passwords was easy enough on 4.2, now how about
*double-length* passwords? or do i have to get the source for the
shadow suite and install it?
--
did verily scribe:
Quote:>conversion to shadowed passwords was easy enough on 4.2, now how about
>*double-length* passwords? or do i have to get the source for the
>shadow suite and install it?
# cd /etc
# pwconv5
# chmod 600 passwd- shadow-
after doing that, i got MD5 longer-than-8-characters passwords by editing
"/etc/pam.d/login", "/etc/pam.d/passwd", and "/etc/pam.d/su", adding "md5"
(and "shadow" if not already there) to the end of the lines that begin with
either "auth" or "password" AND contain the string "/lib/security/pam_pwdb.so".
rebooted, and it worked for me. your mileage may vary, caveat emptor and all
that...
--
1. Toggling single/double length shadow passwords
I am running SLS 1.03 (0.99p14) with shadow passwords enabled.
I have a problem with ftpd and pop3d not being able to recognize
the passwords given, although telnetd has no problem with it.
Someone on this list mentioned that it could be because I have
double-length passwords enabled in shadow.
1. How do I toggle to single length passwords?
2. How can I disable shadow passwords?
3. Is there any way to transfer/convert passwords from the previous
setup to the new setup without having all users on my Linux box
enter a new password?
Thanks in advance, -Borries
2. Dial In Server & Login Prompt
3. shadow passwords and RedHat 4.2
4. SunOS 5.3 setrlimit() bug ?
5. Redhat 4.2 & shadowed passwords.
6. How do I use Shell Variables in sed
7. shadow passwords and RedHat 4.2
8. How to set <DEL> key for 'intr' ?
9. RedHat 4.2 & Shadow Passwords Question.Hi
10. Shadow password files vs. non-shadowed passwords
11. ERROR: KDE shadow password error although no shadow passwords used
12. xdm-shadow & password length
13. Password bug in RedHat 4.2