09-14-2003
Quote:
Originally posted by Perderabo
If that file is empty, I guess that I too would copy it over. But letting root log in without a password is a very extreme move to make. That implies to me that it could not file root's encrypted passord for checking.
If you guys have multiple SCO boxes, surely you must have access to some unix expertise. This seems like a good time to bring in an expert.
I copied that file from another Sco Box, logged off then when I tried to log in , this time it asked me for the password, the crontab returned to work normally, and the machine is allowing remote remote log in, so i guess everything is fine right now.
Thanks.
10 More Discussions You Might Find Interesting
1. Programming
Can you tell me why ? Thank you !
$ cc -L /usr/lib server.c -lsocket
UX:acomp: WARNING: "server.c", line 60: argument is incompatible with prototype6
Undefined first referenced
symbol in file
ffush server.o... (2 Replies)
Discussion started by: loudingyang
2 Replies
2. Shell Programming and Scripting
Hi Engg. ! :mad:
I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Discussion started by: Niraj Gopal Sha
0 Replies
3. Filesystems, Disks and Memory
Hello Moto
I hope someone can help
We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers..
a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Discussion started by: haggo
2 Replies
4. UNIX for Dummies Questions & Answers
my problem is like this
while ftping locally it works,
but when users from WAN try the ftp services it doesnt comes
the message it displays is as follows "connection closed by remote host "
please help
Thanks (5 Replies)
Discussion started by: Athos19
5 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
This is the first time I have attempted to install SCO UNIX. I have a customer that has requested we install it on a desktop sized machine and they have supplied me with their install CD - "SCO UNIX Release 6.0.0 Base Operating System Install disk CD 1"
I am attempting to install it... (0 Replies)
Discussion started by: Becks
0 Replies
6. SCO
Hi, i'm from Argetina and my english is very poor.
I'm trying to copy disk with sco unix 5.0.5 -60Gb IDE
Disk- (7476, 255, 63) to other disk -IDE 80Gb- and g4u v2.3.
After the copy, i'm trying the 80Gb disk and the roblem is the partition /u/disco is empty.
Note: /u/disco is the... (0 Replies)
Discussion started by: sebpes
0 Replies
7. Solaris
Hi All,
When i am trying to restart the inetd daemon it throughing error.
Please find the message and tell me what i need to do ?
Apr 7 22:57:37 HYDOHS01 inetd: ISTATE not in environment
Apr 7 22:57:41 HYDOHS01 inetd: stop: No such file or directory
Apr 7 22:58:01 HYDOHS01 inetd: ... (5 Replies)
Discussion started by: lbreddy
5 Replies
8. SCO
Hi i have a problem after boot with N1 disk and putting N2 disk and pressing the enter in this message:Insert N2(filesystem) floppy and press after by this(pressing enter) the system is reboot!! why??? :confused:
my old pc is a Pentium II 333mhz 3gb hd 64mb ram
please help!! :( (3 Replies)
Discussion started by: panos_pit
3 Replies
9. SCO
Hi
I am looking for sco xenix binary compatibility utility "cvtomf",(convert omf object to COFF object)
Would you please help me ?
tnx (3 Replies)
Discussion started by: javad1_maroofi
3 Replies
10. SCO
Hi
I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7.
I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies
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)