a) Why does /etc/passwd belong to roy roy, and not to root shadow?
This is really unsafe.
Quote:
b) Do you see that "L" here above?
Your account looks locked.
From man passwd:
Quote:
-l, --lock
Lock the password of the named account. This option disables a password by changing it
to a value which matches no possible encrypted value (it adds a ´!´ at the beginning
of the password).
Note that this does not disable the account. The user may still be able to login using
another authentication token (e.g. an SSH key). To disable the account, administrators
should use usermod --expiredate 1 (this set the account's expire date to Jan 2, 1970).
Users with a locked password are not allowed to change their password.
[...]
-u, --unlock
Unlock the password of the named account. This option re-enables a password by
changing the password back to its previous value (to the value before using the -l
option).
This should explain why here below you have two r, instead of a w and a u:
Quote:
To confirm, could you post the output of: # grep roy /etc/shadow?
No fear: you're there, you have physical access to the system, so you can do anything. This problem will be solved.
--
Bye
i messed up while installing freebsd into a dual os wannabe system.
Now, how do i del it( so i wouldn't get prompted to choose freebsd during boot?)so that i could try installing a different flavour of linux?
cheers:eek: (1 Reply)
I created tar files for directories using this command:
tar -cvf * >tarfile
what happened was I got a file tarfile with a list of the files and it took the first file in each directory and overwrote it with the actual tar file. I've been trying to figure out since yesterday what I did... (2 Replies)
Hi
Guy,
In my system there were some cronjob were already scheduled. and somehow I want to enter one new cronjob with crontab. So I isssue crontab temp.txt. it scheduled that job but now it's showing me only this job with crontab -l. but I can not see the old cronjob list that already set up.... (2 Replies)
Dear Friends,
I have messed up with my .bashrc file (something I have deleted) and now i can't login back to system..
any Idea..
I can do login with other login and password.. but I dont have root password because of security reason...
If I ask root then It will take about 4 -5 days to go... (4 Replies)
Ok, a couple weeks ago I was fixing a cron report about perl not happy with 'locale' info (LANG and LC not set). As a result, I was experimenting with setting the correct 'locale' in several areas (like /etc/sysconfig/i18n and who knows where). Somehow after a reboot, as soon as the OS starts... (3 Replies)
Hi,
Just wanted to know if anyone else has noted that the time-stamp in the history is all out of whack.:eek:
I've Ubuntu, all patched, and when I ran history, it showed me commands that I ran few weeks ago with today's date. Is this normal?
Here is a snippet:
....
85 2010-06-09 09:03:31... (6 Replies)
Help!!
Seem to have messed up my path, as I keep getting command not found error. Could someone please tell whats wrong or how to fix it.
export PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:$PATH
---------- Post updated at 08:34 PM ---------- Previous update was at 07:50 PM ----------
... (1 Reply)
I have AIX 5.3 with oracle 10g ( test server). While trying to create RAW disk for Oracle ASM I have accidentally messed with rootvg (hdisk0 & hdisk1)
When I do
# lspv hdisk0
0516-066 : Physical volume is not a volume group member.
Check the physical volume name specified. ... (4 Replies)
OK, so I just messed myself up. Thinking the /var/opt/ignite/data/INDEX files was static, I manually edited the file and added 2 more OS's to it. During an Install it only showed the first OS (started with 11.31, 3 versions then added a 11.23, and a 11.11 stanza's).
The 11.23 and 11.11 never... (2 Replies)
Discussion started by: mrmurdock
2 Replies
LEARN ABOUT MINIX
shadow
SHADOW(5) File Formats and Conversions SHADOW(5)NAME
shadow - shadowed password file
DESCRIPTION
shadow is a file which contains the password information for the system's accounts and optional aging information.
This file must not be readable by regular users if password security is to be maintained.
Each line of this file contains 9 fields, separated by colons (":"), in the following order:
login name
It must be a valid account name, which exist on the system.
encrypted password
Refer to crypt(3) for details on how this string is interpreted.
If the password field contains some string that is not a valid result of crypt(3), for instance ! or *, the user will not be able to
use a unix password to log in (but the user may log in the system by other means).
This field may be empty, in which case no passwords are required to authenticate as the specified login name. However, some
applications which read the /etc/shadow file may decide not to permit any access at all if the password field is empty.
A password field which starts with an exclamation mark means that the password is locked. The remaining characters on the line
represent the password field before the password was locked.
date of last password change
The date of the last password change, expressed as the number of days since Jan 1, 1970.
The value 0 has a special meaning, which is that the user should change her password the next time she will log in the system.
An empty field means that password aging features are disabled.
minimum password age
The minimum password age is the number of days the user will have to wait before she will be allowed to change her password again.
An empty field and value 0 mean that there are no minimum password age.
maximum password age
The maximum password age is the number of days after which the user will have to change her password.
After this number of days is elapsed, the password may still be valid. The user should be asked to change her password the next time
she will log in.
An empty field means that there are no maximum password age, no password warning period, and no password inactivity period (see below).
If the maximum password age is lower than the minimum password age, the user cannot change her password.
password warning period
The number of days before a password is going to expire (see the maximum password age above) during which the user should be warned.
An empty field and value 0 mean that there are no password warning period.
password inactivity period
The number of days after a password has expired (see the maximum password age above) during which the password should still be accepted
(and the user should update her password during the next login).
After expiration of the password and this expiration period is elapsed, no login is possible using the current user's password. The
user should contact her administrator.
An empty field means that there are no enforcement of an inactivity period.
account expiration date
The date of expiration of the account, expressed as the number of days since Jan 1, 1970.
Note that an account expiration differs from a password expiration. In case of an account expiration, the user shall not be allowed to
login. In case of a password expiration, the user is not allowed to login using her password.
An empty field means that the account will never expire.
The value 0 should not be used as it is interpreted as either an account with no expiration, or as an expiration on Jan 1, 1970.
reserved field
This field is reserved for future use.
FILES
/etc/passwd
User account information.
/etc/shadow
Secure user account information.
/etc/shadow-
Backup file for /etc/shadow.
Note that this file is used by the tools of the shadow toolsuite, but not by all user and password management tools.
SEE ALSO chage(1), login(1), passwd(1), passwd(5), pwck(8), pwconv(8), pwunconv(8), su(1), sulogin(8).
shadow-utils 4.5 01/25/2018 SHADOW(5)