9 More Discussions You Might Find Interesting
1. HP-UX
is there a way for my C++ application to find out which mode the hpux OS is running in?
standard mode or trusted mode. (3 Replies)
Discussion started by: einsteinBrain
3 Replies
2. Ubuntu
Hi Experts,
I am using ubuntu.When i am trying to login it is showing grub ..How i can overcome to this problem..Pls reply me ASAP..
Thanks,
Sree (1 Reply)
Discussion started by: sree vasu
1 Replies
3. 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
4. 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
5. BSD
Hello!
I am new to the forum and I need help on restoring root user's password or access the form of single user mode under operating system very long-standing family bsd - Unix system V I think it's also called srv4. I managed to enter the owner of IPL, and a moment after the rise of system... (2 Replies)
Discussion started by: hmalool
2 Replies
6. Solaris
Hi All,
I got a big problem here.
While setting up a sun cluster, I accidentally tried out "bootadm update-archive" as I was unable to bring the cluster up.
After which, i tried a reconfiguration reboot.
Now The system is always booting into maintanence mode with error message... (8 Replies)
Discussion started by: manojsomanath
8 Replies
7. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
8. Solaris
Dear Frnds,
I have a weird issue with solaris 10.
We bought a new Sun Ultra45 workstation and i installed solaris 10 in that.
The problem is when it goes to standby mode i am not able to resume the system.The only thing i can do is to manually reboot and start working.
The problem occurs... (0 Replies)
Discussion started by: sriram.s
0 Replies
9. Solaris
Hi
Im using a Sun blade 1500 with solaris 8 and when the monitor goes to stand by mode, the machine doesnt return to the normal mode anymore. Then i have to reboot it always.
Does anybody have a clue how can i solve it or turn off the stand by mode?
Thanks (2 Replies)
Discussion started by: dougpss
2 Replies
sulogin(8) System Manager's Manual sulogin(8)
NAME
sulogin - single-user login program (Enhanced Security)
SYNOPSIS
/sbin/sulogin
DESCRIPTION
The sulogin program is run by the init process on the console terminal when entering single-user mode. The sulogin program checks the sys-
tem configuration to determine whether entering single-user mode requires entering the root password. If it does not, then sulogin execs
/sbin/sh with its argv[0] set to "-". That same exec is also done if the root password is correctly entered.
The decision to enter the single-user mode depends on the state of the system configuration files. If the files cannot be read, then
defaults are assumed (as described below). Therefore, the loss of a configuration file does not prevent access to the system console for
repairing the problem.
The sulogin program first checks the /etc/rc.config file for a the SECURE_CONSOLE variable. If such a variable is present, and it is set
to a true value (either "TRUE", "ON", "YES", or "1"), then the program asks for the root password. The value of the SECURE_CONSOLE vari-
able is checked in a case-independent fashion, and only a minimal match is necessary. Thus, the value is really checked against the fol-
lowing regular expression:
^([Tt]|1|[Yy]|[Oo][Nn]).*
If the SECURE_CONSOLE variable is present, but does not have one of the true values, then sulogin does not ask for the root password, but
simply execs /sbin/sh as previously described.
If the SECURE_CONSOLE variable is not found in the /etc/rc.config file, or if that file is missing or unreadable, then an attempt is made
to obtain the value of the console firmware setting of the SECURE variable, using the GSI_PROM_ENV function of the getsysinfo() system
call. If the check determines the console commands are password- protected, the sulogin program requests the root password.
If sulogin has made the decision to request the root password, it also determines whether BASE or ENHANCED security should be used to vali-
date that password. This is done using the value of the SECURITY variable from the /etc/rc.config file, unless that file was not readable,
in which case the /etc/sia/matrix.conf file is read, looking for a line beginning with the string "siad_ses_init=", and containing either
"(OSFC2," or "(BSD,". If the /etc/rc.config file was readable, but the SECURITY variable was not set, then BASE security is assumed.
(This is how the /sbin/init.d/security script initializes the /etc/sia/matrix.conf file, as well). If the /etc/rc.config file can not be
read and the /etc/sia/matrix.conf file either can not be read or does not have an appropriate siad_ses_init line, then the sulogin program
checks to see whether the /etc/passwd file contains a valid entry for root and whether the getespwnam("root") function returns a valid
extended profile. If both profile entries exist, but only one has a valid encrypted password field, that profile (and thus that security
policy) is used. If both passwords are valid, the BASE security policy is used.
Once the sulogin program has determined which security policy to use, it checks whether that policy has a valid account entry for user root
(if not already checked while determining which policy to use), and whether that entry has a password that can be matched. If the password
is impossible to match, or if no valid root profile exists, then sulogin prints a warning and execs /sbin/sh as previously described. For
BASE security, a null encrypted password field for root causes the program to exec /sbin/sh without complaining.
If there is a matchable root password, sulogin prints out "Single-user root login" and prompts for the password. If the entered password
does not match (after the appropriate encryption if non-null), the program waits for 5 seconds (to deter break-in attempts, displays
"Sorry", and re-prompts. If the program is interrupted or receives and end-of-file condition while attempting to read a password from the
console terminal, it simply exits. This normally causes init to enter multi-user mode (It depends on system configuration information in
/etc/inittab, specifically the entry marked with "initdefault", which ships at run-level "3"). This may also cause init to prompt for a
run level, or to restart the sulogin program.
Finally, if a password was collected, and it did match, the exec of /sbin/sh is done. If that exec fails, the reason for the failure is
displayed, and the program sleeps for 5 seconds before exiting. Upon exiting control of the console is returned to the init process, as
previously described for interrupt or end-of-file.
FILES
/etc/rc.config
/etc/sia/matrix.conf
/etc/passwd
/tcb/files/auth.db (/tcb/files/auth/r/root)
RELATED INFORMATION
login(1), getpwnam(3), getespwnam(3), dispcrypt(3), matrix.conf(4), init(8)
Security delim off
sulogin(8)