05-27-2005
This is not a safe request. Why would you cater to this user's inablility to remember a password?
Is it the CEO?
10 More Discussions You Might Find Interesting
1. Solaris
How to set passwd history feature in Solaris 8 to stop users from using their old passwords? (4 Replies)
Discussion started by: amoorti
4 Replies
2. UNIX for Dummies Questions & Answers
Hi...
i have one doubt pls...
1)can we clear the command line history in UNIX for a paricular login(scadm/root)if so how?.
2) can we see the time at which command executed.
history is showing like :
100 display
101 lock
102 exit (7 Replies)
Discussion started by: gincemathew
7 Replies
3. Solaris
hi
Any one can help me. I am using Sun_Solaris. The command history set to 100 at .cshrc. I am unable to clear the command histoy. In Linux it is very easy by giving command
history -c
I could not find any such type command to clear the history.
Is there any such type of command for solaris.... (3 Replies)
Discussion started by: prabir
3 Replies
4. Shell Programming and Scripting
Hi,
I would normally clear off the history entries from a terminal by using the following commands:
> ~/.bash_history
history -c
But this will remove the entries of that particular session only. How to prune all the entries of all login sessions for a particular user in a system?
N.B:... (3 Replies)
Discussion started by: royalibrahim
3 Replies
5. UNIX for Dummies Questions & Answers
Hello All, Good Morning.
I am trying to erase history list in my linux box, but my below command is failing. What is the actual way to clear it?
> history clear
-bash: history: clear: numeric argument required
Also when I run my commands in my command prompt, my team lead can see my... (7 Replies)
Discussion started by: NARESH1302
7 Replies
6. Solaris
Hi Folks,
I have Solaris 10, latest release.
We have passwd aging set in /etc/defalut/passwd.
I have an account that passwd should never expire. Acheived by emptying associated users shadow file entries for passwd aging.
When I reset the users passwd using passwd command, it re enables... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
7. Shell Programming and Scripting
I want to clear the history so that no one should be able to see what commands I gave in the AIX OS level. I tried using history -c , ~/.sh_history, but they aren't working :wall:
Please tell me the command in ksh which can clear all the previous history? (4 Replies)
Discussion started by: lg123
4 Replies
8. AIX
Does anyone know when AIX started using /etc/security/passwd instead of /etc/passwd to store encrypted passwords? (1 Reply)
Discussion started by: Anne Neville
1 Replies
9. Shell Programming and Scripting
Hi
Am using ksh shell
I need to remove history of commands used..
I tried
# rm .vi_history
# touch .vi_history
# chmod 600 .vi_history
This didnt work.. I tried also
# rm .sh_history
# touch .sh_history
# chmod 600 .sh_history (5 Replies)
Discussion started by: Priya Amaresh
5 Replies
10. UNIX for Dummies Questions & Answers
As in the title, how to clear the history entries?
For eg: if i enter history, series of linux commands getting displayed from day 1. I need to clear those entries and want linux commands to be stored freshly.
Thanks in advance (6 Replies)
Discussion started by: karthick nath
6 Replies
LEARN ABOUT CENTOS
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. Value of 0 makes the module to keep the
existing contents of the opasswd file unchanged.
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 09/19/2013 PAM_PWHISTORY(8)