12-17-2018
Hi MadeInGermany,
I completely agree, I remember running crack against the pw file from a bunch of Siemens Nixdorf machines running Reliant SVR4 back in the early 90's and yes the most common password was ........."password". I have to keep my passwords in a key-ring as I now have in excess of 200, where systems have differing levels of complexity - I did keep them in an encrypted spread sheet on my encrypted USB stick until the WinTel team remotely imaged my Laptop and disabled the USB ports - but then that's progress.
Now I work in a much more sanitised environment and along with the password complexity rules and the 2FA, it sometimes takes me longer to navigate to the console of a server - than it does to fix the problem - I just love working in IT!
Also remember that three wrong attempts and you had to wait 60s before trying again - from memory if you got it wrong on an other three attempts the wait went up to five minutes or it might have been fifteen.
Gull04
4 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear all,
I need to automate/script a user password change process. I'm helpless cannot use expect since it's not installed and cannot install it either. Do i have an alternative. I can store the password in a file and that would be the password that would be set to all the users. If not i don't... (1 Reply)
Discussion started by: earlysame55
1 Replies
2. UNIX for Advanced & Expert Users
I've been using various versions of UNIX and Linux since 1993, and I've never run across one that showed your password as you type it in when you log in, or one that stored passwords in plain text rather than encrypted. I'm writing a script for work for a security audit, and two of the... (5 Replies)
Discussion started by: Anne Neville
5 Replies
3. What is on Your Mind?
What is on Your Mind?
2018 FIFA World Cup - Wikipedia
I'm hoping that England are drawn into positions B2, D3, G3 or G4 so that all their games will be outside usual UK office hours and people will not desert the office with mystery illnesses to watch the games.
Expecting failure, so I... (1 Reply)
Discussion started by: rbatte1
1 Replies
4. What is on Your Mind?
Happy Holidays.
Here are my randoms thought at the end of 2018 in no particular order.
You Are Truly Blessed
IT people are lucky. We get to use our brains extensively to solve complex and challenging computer-technology related problems. This is very good for our brains. Programming,... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT SUSE
pam_pwhistory
PAM_PWHISTORY(8) Linux-PAM Manual PAM_PWHISTORY(8)
NAME
pam_pwhistory - PAM module to remember last passwords
SYNOPSIS
pam_pwhistory.so [debug] [use_authtok] [enforce_for_root] [remember=N] [retry=N] [authtok_type=STRING]
DESCRIPTION
This module saves the last passwords for each user in order to force password change history and keep the user from alternating between the
same password too frequently.
This module does not work together with kerberos. In general, it does not make much sense to use this module in conjunction with NIS or
LDAP, since the old passwords are stored on the local machine and are not available on another machine for password history checking.
OPTIONS
debug
Turns on debugging via syslog(3).
use_authtok
When password changing enforce the module to use the new password provided by a previously stacked password module (this is used in the
example of the stacking of the pam_cracklib module documented below).
enforce_for_root
If this option is set, the check is enforced for root, too.
remember=N
The last N passwords for each user are saved in /etc/security/opasswd. The default is 10.
retry=N
Prompt user at most N times before returning with error. The default is 1.
authtok_type=STRING
See pam_get_authtok(3) for more details.
MODULE TYPES PROVIDED
Only the password module type is provided.
RETURN VALUES
PAM_AUTHTOK_ERR
No new password was entered, the user aborted password change or new password couldn't be set.
PAM_IGNORE
Password history was disabled.
PAM_MAXTRIES
Password was rejected too often.
PAM_USER_UNKNOWN
User is not known to system.
EXAMPLES
An example password section would be:
#%PAM-1.0
password required pam_pwhistory.so
password required pam_unix.so use_authtok
In combination with pam_cracklib:
#%PAM-1.0
password required pam_cracklib.so retry=3
password required pam_pwhistory.so use_authtok
password required pam_unix.so use_authtok
FILES
/etc/security/opasswd
File with password history
SEE ALSO
pam.conf(5), pam.d(5), pam(8) pam_get_authtok(3)
AUTHOR
pam_pwhistory was written by Thorsten Kukuk <kukuk@thkukuk.de>
Linux-PAM Manual 04/01/2010 PAM_PWHISTORY(8)