Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 02:12 AM
05-30-2002 02:12 AM
Can it be used to prompt for a password when entering the system maintenance or single user mode??
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 02:16 AM
05-30-2002 02:16 AM
Re: sulogin
/var/adm/sulog
and no, you cant prompt for a password if someone boots in lvm maintenance mode or single user mode. Dont leave the key in service mode on the server and then nobody can boot in single user mode or maintenance mode without the key!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 02:18 AM
05-30-2002 02:18 AM
Re: sulogin
trusted would be best solution.
convert to a trusted system :
Within SAM you can set up the system security policies so that a
login is required when booting the system to single user.
This can be enabled as follows:
SAM --> Auditing and Security --> System security Policies -->
General User Account Policies : enable "Require login upon boot
to single user state"
The root account by default will have authority to boot the
system to single user.
You can then authorise a particular user to boot to single user
SAM --> Accounts For Users and Groups --> select the user --->
Modify Users Security Policy --> General User Account Policies
and enable " Authorize user to Boot to single-User state" .
The "Boot authentication prompt " is displayed if the "Require
login Upon Boot to single user state" is enabled and the system
is booted to single user.
steve Steel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 02:58 AM
05-30-2002 02:58 AM
Re: sulogin
Clarification please.
Does your solution mean that the root account will also be prompted for a password when entering single user mode??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 03:10 AM
05-30-2002 03:10 AM
Solutionfirst of all to say: As all the others allready said, change to a trusted system!
To give the answer to your question: YES, then even root is prompted for a password when booting into single user mode. Only possibility to get into the system then is to use installation CD- ROM and remount the file systems to get in write- mode and then remove root password from tcb- directory.
Please don't forget also to secure your web console. (If you have a computer which has one...) Go into service processor mode and enter HE or LI at prompt to find information which commands you need to activate.
Allways stay on the bright side of life!
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 03:12 AM
05-30-2002 03:12 AM
Re: sulogin
peter got it in one.
If you want security then apply it by making the system trusted.
steve Steel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 04:58 PM
05-30-2002 04:58 PM
Re: sulogin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 05:27 PM
05-30-2002 05:27 PM
Re: sulogin
A trusted system will have a protected password file: '/tcb/files/auth/'.
A trusted system (most visibly) displays the message "last successful/unsuccessful login..." upon user logon. This is a dead-give-away of a trusted server.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 05:33 PM
05-30-2002 05:33 PM
Re: sulogin
1) This is the direct approach (definitive and quickest):
# /etc/tsconvert
System has already been converted.
If your system has already been converted, tsconvert will show the status by printing the message stating that your system has already been converted.
Other methods include:
2) Not surest method but one of the quickest methods:
# ll -d /tcb
Check for /tcb existence. /tcb is created upon conversion.
3) One definitive way (one long method):
The definitive way (this is just one way) is to check it from SAM:
SAM
-> Audit and Security
-> Audited Events
If your system is not trusted, you will see a popup dialog saying that your system is not trusted, and ask you whether you wish to convert it to trusted.
Once trusted, under "Actions",
you will notice the option to: "Unconvert the system"
Hope this helps. Regards.
Steven Sim Kok Leong