11-19-2017
I would be careful with rolemod. Not that at the end root lost its superuser role and cannot gain it back...
You see, I have never used rolemod.
I would rather save /etc/shadow (with cp to a new file) or save root's password hash.
Then set a new root password. Then reboot to single-user, now typing the root password, patching the OS, and reboot.
When everything is nice and shiny again, you can restore the shadow file (with cp) or root's password hash, so the old unknown password is back.
10 More Discussions You Might Find Interesting
1. HP-UX
hi,
i figured why i need to boot in MMB,some of which are missing or corrupt LABEL (LIF labeL ,i guess) on the boot disk.
To explicitly corrupt this entry i think a simple dd will work.
ok let me elaborate this issue:
i need to check this functionality.
so i have one LVM boot disk
and one... (0 Replies)
Discussion started by: mxms755
0 Replies
2. Solaris
I had a power failure the other day and when my relatively new Solaris 10 machine rebooted it is thrown into maintenance mode.
I've found the following lines in the /var/adm/messages file, I'm assuming this is the root cause of the problem. However, I don't have the slightest idea on how to... (9 Replies)
Discussion started by: cheetobandito
9 Replies
3. Solaris
Hello All,
On solaris 10 server i could see the FTP service is in maintenance mode always :mad:
Could some assist?
svcs -xv
svc:/network/nfs/nlockmgr:default (NFS lock manager)
State: maintenance since Tue 28 Jul 2009 11:47:55 AM BST
Reason: Restarting too quickly.
See: Sun... (5 Replies)
Discussion started by: bullz26
5 Replies
4. Solaris
Hi,
I have installed Hudson on a Solaris 11 server, using the installation instructions available at Paul Oswald: Hudson Solaris SMF Manifest.
When I perform svcs -l hudson, I get:
fmri svc:/application/hudson:default
name Hudson Continuous Build Server
enabled true... (4 Replies)
Discussion started by: JVerstry
4 Replies
5. Solaris
I have a Solaris 10 SunFire v880 machine and I'm having trouble with Samba.
Samba has worked on this machine but since the machine has been re-booted Samba has not worked.
Machine details are:
cat /etc/release
Solaris 10 10/08 s10s_u6wos_07b SPARC
Copyright 2008... (2 Replies)
Discussion started by: KenLynch
2 Replies
6. Solaris
Hi Guys,
I have a sunblade 1500. I booted the system and it booted to maintenance mode. How can I fix this?
Thanks lots (8 Replies)
Discussion started by: cjashu
8 Replies
7. Solaris
I have seen similar threads on this issue, but I have not seen a fix. Basically I am getting a lot of rcp bind errors. Below find the output of "svcs -xv". not sure where to begin:
# svcs -xv
svc:/network/rpc/bind:default (RPC bindings)
State: maintenance since Fri May 25 14:13:18 2012... (14 Replies)
Discussion started by: brownwrap
14 Replies
8. Solaris
:confused:
when i tried to look the status of DNS-client, it is in maintenance mode.....
Please tell me how to bring it back to online mode...PLEASE TELL ME STEP BY STEP.... PLEASE...
:wall: (2 Replies)
Discussion started by: vamshigvk475
2 Replies
9. Solaris
All I'm running an OpenSolaris system (Nexenta). When doing a svcs I see that/network/smb/server is in maintenance mode.
I have run a clear on the service and restarted. I see the same service show online* for a bit but then, enters maintenance every time.
In the service log I... (2 Replies)
Discussion started by: dcpatriot
2 Replies
10. AIX
Hi this may be a easy question to answer but thanks in advance.
So I was able to download the VIOS media from IBM and currently I am burning it to a cd/dvd right now.
The steps I've collected so far are from the net. can you please confirm and add on to the steps if there are any steps... (0 Replies)
Discussion started by: Adnans2k
0 Replies
d_passwd(4) File Formats d_passwd(4)
NAME
d_passwd - dial-up password file
SYNOPSIS
/etc/d_passwd
DESCRIPTION
A dial-up password is an additional password required of users who access the computer through a modem or dial-up port. The correct pass-
word must be entered before the user is granted access to the computer.
d_passwd is an ASCII file which contains a list of executable programs (typically shells) that require a dial-up password and the associ-
ated encrypted passwords. When a user attempts to log in on any of the ports listed in the dialups file (see dialups(4)), the login program
looks at the user's login entry stored in the passwd file (see passwd(4)), and compares the login shell field to the entries in d_passwd.
These entries determine whether the user will be required to supply a dial-up password.
Each entry in d_passwd is a single line of the form:
login-shell:password:
where
login-shell The name of the login program that will require an additional dial-up password.
password An encrypted password. Users accessing the computer through a dial-up port or modem using login-shell will be required to
enter this password before gaining access to the computer.
d_passwd should be owned by the root user and the root group. The file should have read and write permissions for the owner (root) only.
If the user's login program in the passwd file is not found in d_passwd or if the login shell field in passwd is empty, the user must sup-
ply the default password. The default password is the entry for /usr/bin/sh. If d_passwd has no entry for /usr/bin/sh, then those users
whose login shell field in passwd is empty or does not match any entry in d_passwd will not be prompted for a dial-up password.
Dial-up logins are disabled if d_passwd has only the following entry:
/usr/bin/sh:*:
EXAMPLES
Example 1: Sample d_passwd file.
Here is a sample d_passwd file:
/usr/lib/uucp/uucico:q.mJzTnu8icF0:
/usr/bin/csh:6k/7KCFRPNVXg:
/usr/bin/ksh:9df/FDf.4jkRt:
/usr/bin/sh:41FuGVzGcDJlw:
Generating An Encrypted Password
The passwd (see passwd(1)) utility can be used to generate the encrypted password for each login program. passwd generates encrypted pass-
words for users and places the password in the shadow (see shadow(4)) file. Passwords for the d_passwd file will need to be generated by
first adding a temporary user id using useradd (see useradd(1M)), and then using passwd(1) to generate the desired password in the shadow
file. Once the encrypted version of the password has been created, it can be copied to the d_passwd file.
For example:
1.
Type useradd tempuser and press Return. This creates a user named tempuser.
2. Type passwd tempuser and press Return. This creates an encrypted password for tempuser and places it in the shadow file.
3. Find the entry for tempuser in the shadow file and copy the encrypted password to the desired entry in the d_passwd file.
4. Type userdel tempuser and press Return to delete tempuser.
These steps must be executed as the root user.
FILES
/etc/d_passwd dial-up password file
/etc/dialups list of dial-up ports requiring dial-up passwords
/etc/passwd password file
/etc/shadow shadow password file
SEE ALSO
passwd(1), useradd(1M), dialups(4), passwd(4), shadow(4)
WARNINGS
When creating a new dial-up password, be sure to remain logged in on at least one terminal while testing the new password. This ensures
that there is an available terminal from which you can correct any mistakes that were made when the new password was added.
SunOS 5.10 2 Sep 2004 d_passwd(4)