Are you in trusted mode? You can tell by looking to see if there are files under /tcb/files/auth If there is, then under this point, there is one character a directory for the first of each user name and within there, there is a file for each user. Look at the timestamp of the file to see the last update of it, however if it has been attacked (someone tried to use it) then this will have been updated.
Within, there are fields describing last successful login, last failed login, last password update etc. The times recorded are in seconds from 1/1/1970 00:00:00 (the Epoch) so someone here helpfully wrote this bit of Perl that reformats it to make it human readable:-
I have this as a one-line script, so I just run something like:-
Code:
$ realtime 1234567890
Fri Feb 13 23:31:30 2009
I hope that this helps. If you are not in trusted mode, then it depends if you clean out the login history files (whatever they are) Try using the last command. Read the manual pages for the options. It might be useful, maybe not. Unless you intercept and log every use of the various user admin commands (useradd, modprpw, passwd etc.) it's going to be difficult to really prove anything.
As a more general question though, are the auditors complaining that the id they used last time to probe around has been suspended? If it's more that a month since they last used it, then I think you have every right to suspend it to limit the risk of attack, in fact you could argue that it should be suspended immediately after they have finished using it.
i understand they have an important job to do, but sometimes they are the worst offenders just asking for open access whenever they want it. Enforce your standards, especially with them. It could be a test of your procedures
hi all, i m tryin to create a new account on the unix work station. do i use 'useradd' command? can u guyz advice on the usage of 'useradd' command as it can comes with 'useradd -D' or 'useradd -e'
thanks :confused: (1 Reply)
Hi, guys. I have two questions:
I need to write a script, which can show all the non-suspended users on system, and suspend the selected user account.
There are two things I am not sure:
1. How can I suspend user's account? What I think is: add a string to the encrypted password in shadow... (2 Replies)
Hi Admins,
As per my knowledge there are two types of user accounts in unix. root and normal users.
If there are any user types for which we can give some priviledges..?
Actually i want to restrict root access and create new accounts for admins with some of the priviledges.
Please let me... (6 Replies)
Hi - I want to log commands typed by oraapps user with time into some log file on runtime.
HISTTIMEFORMAT="%d/%m/%y %T " works but any one with oraapps user can delete the history.
OS : RHEl 5.6
Any help is appreciated. (5 Replies)
Discussion started by: oraclermanpt
5 Replies
LEARN ABOUT BSD
chsh
CHPASS(1) General Commands Manual CHPASS(1)NAME
chpass - add or change user database information
SYNOPSIS
chpass [ -a list ] [ user ]
DESCRIPTION
Chpass allows editing of the user database information associated with user or, by default, the current user. The information is formatted
and supplied to an editor for changes. The vi editor will be used unless the environmental variable EDITOR selects an alternate editor.
When the editor terminates, the information is re-read and used to update the user database itself. Only the user, or the super-user, may
edit the information associated with the user.
Only the information that the user is allowed to change is displayed.
Possible display items are as follows:
Login: user's login name
Password: user's encrypted password
Uid: user's id
Gid: user's login group id
Change: password change time
Expire: account expiration time
Class: user's general classification
Home Directory: user's home directory
Shell: user's login shell
Full Name: user's real name
Location: user's normal location
Home Phone: user's home phone
Office Phone: user's office phone
The login field is the user name used to access the computer account.
The password field contains the encrypted form of the user's password.
The uid field is the number associated with the login field. Both of these fields should be unique across the system (and often across a
group of systems) as they control file access.
While it is possible to have multiple entries with identical login names and/or identical user id's, it is usually a mistake to do so.
Routines that manipulate these files will often return only one of the multiple entries, and that one by random selection.
The group field is the group that the user will be placed in upon login. Since this system supports multiple groups (see groups(1)) this
field currently has little special meaning. This field may be filled in with either a number or a group name (see group(5)).
The change field is the date by which the password must be changed.
The expire field is the date on which the account expires.
Both the change and expire fields should be entered in the form ``month day year'' where month is the month name (the first three charac-
ters are sufficient), day is the day of the month, and year is the year.
The class field is currently unused. In the near future it will be a key to a termcap(5) style database of user attributes.
The user's home directory is the full UNIX path name where the user will be placed on login.
The shell field is the command interpreter the user prefers. If the shell field is empty, the Bourne shell (/bin/sh) is assumed.
When altering a login shell, and not the super-user, the user must select an approved shell from the list in /etc/shells.
The last four fields are for storing the user's full name, office location, and home and work telephone numbers.
The super-user is also allowed to directly supply a user database entry, in the format specified by passwd(5), as an argument to the -a
option. This argument must be a colon (``:'') separated list of all the user database fields, although they may be empty.
Once the information has been verified, chpass uses mkpasswd(8) to update the user database. This is run in the background, and, at very
large sites could take several minutes. Until this update is completed, the password file is unavailable for other updates and the new
information will not be available to programs.
FILES
/etc/master.passwd The user database /etc/shells The list of approved shells
SEE ALSO login(1), finger(1), getusershell(3), passwd(5), mkpasswd(8), vipw(8)
Robert Morris and Ken Thompson, UNIX password security
BUGS
User information should (and eventually will) be stored elsewhere.
4th Berkeley Distribution March 12, 1989 CHPASS(1)
06-20-2013
