|Skip Navigation Links|
|Exit Print View|
|Trusted Extensions Configuration and Administration Oracle Solaris 11.1 Information Library|
The following task map describes common administrative procedures in Trusted Extensions.
Trusted Extensions provides a GUI for changing your password.
For the steps, see How to Enter the Global Zone in Trusted Extensions.
If separate passwords are created per zone, the menu can read Change Workspace Password.
Under the following conditions, labeled zones must be rebooted:
One or more local users have changed their passwords.
All zones are using a single instance of the naming service cache daemon (nscd).
The system is administered with files, not LDAP.
Before You Begin
You must be assigned the Zone Security rights profile.
Use one of the following methods:
# txzonemgr &
In the Labeled Zone Manager, navigate to the labeled zone and from the list of commands, select Halt, then select Boot.
You can choose to shut down or halt the system.
The zlogin command cleanly shuts down the zone.
# zlogin labeled-zone shutdown -i 0 # zoneadm -z labeled-zone boot
The halt subcommand bypasses the shutdown scripts.
# zoneadm -z labeled-zone halt # zoneadm -z labeled-zone boot
To automatically update user passwords for labeled zones, you must either configure LDAP or configure one naming service per zone. You can also configure both.
To configure LDAP, see Chapter 5, Configuring LDAP for Trusted Extensions (Tasks).
Configuring one naming service per zone requires advanced networking skills. For the procedure, see How to Configure a Separate Name Service for Each Labeled Zone.
The “Secure Attention” key combination can be used to break a pointer grab or a keyboard grab by an untrusted application. The key combination can also be used to verify if a pointer or a keyboard has been grabbed by a trusted application. On a multiheaded system that has been spoofed to display more than one trusted stripe, this key combination warps the pointer to the authorized trusted stripe.
Press the keys simultaneously to regain control of the current desktop focus. On the Sun keyboard, the diamond is the Meta key.
If the grab, such as a pointer, is not trusted, the pointer moves to the stripe. A trusted pointer does not move to the trusted stripe.
Press the keys simultaneously to regain control of the current desktop focus on your laptop.
Example 9-1 Testing If the Password Prompt Can Be Trusted
On an x86 system that is using a Sun keyboard, the user has been prompted for a password. The cursor has been grabbed, and is in the password dialog box. To check that the prompt is trusted, the user presses the <Meta> <Stop> keys simultaneously. When the pointer remains in the dialog box, the user knows that the password prompt is trusted.
If the pointer had moved to the trusted stripe, the user would know that the password prompt could not be trusted, and contact the administrator.
Example 9-2 Forcing the Pointer to the Trusted Stripe
In this example, a user is not running any trusted processes but cannot see the mouse pointer. To bring the pointer to the center of the trusted stripe, the user presses the <Meta> <Stop> keys simultaneously.
This procedure provides an internal hexadecimal representation of a label. This representation is safe for storing in a public directory. For more information, see the atohexlabel(1M) man page.
Before You Begin
You must be in the Security Administrator role in the global zone. For details, see How to Enter the Global Zone in Trusted Extensions.
$ atohexlabel "CONFIDENTIAL : INTERNAL USE ONLY" 0x0004-08-48
The string is not case-sensitive, but whitespace must be exact. For example, the following quoted strings return a hexadecimal label:
"CONFIDENTIAL : INTERNAL USE ONLY"
"cnf : Internal"
"confidential : internal"
The following quoted strings return a parsing error:
$ atohexlabel -c "CONFIDENTIAL NEED TO KNOW" 0x0004-08-68
Note - Human readable sensitivity labels and clearance labels are formed according to rules in the label_encodings file. Each type of label uses rules from a separate section of this file. When a sensitivity label and a clearance label both express the same underlying level of sensitivity, the labels have identical hexadecimal forms. However, the labels can have different human readable forms. System interfaces that accept human readable labels as input expect one type of label. If the text strings for the label types differ, these text strings cannot be used interchangeably.
In the label_encodings file, the text equivalent of a clearance label does not include a colon (:).
Example 9-3 Using the atohexlabel Command
When you pass a valid label in hexadecimal format, the command returns the argument.
$ atohexlabel 0x0004-08-68 0x0004-08-68
When you pass an administrative label, the command returns the argument.
$ atohexlabel admin_high ADMIN_HIGH atohexlabel admin_low ADMIN_LOW
The error message atohexlabel parsing error found in <string> at position 0 indicates that the <string> argument that you passed to atohexlabel was not a valid label or clearance. Check your typing, and check that the label exists in your installed label_encodings file.
This procedure provides a way to repair labels that are stored in internal databases. For more information, see the hextoalabel(1M) man page.
Before You Begin
You must be in the Security Administrator role in the global zone.
$ hextoalabel 0x0004-08-68 CONFIDENTIAL : NEED TO KNOW
$ hextoalabel -c 0x0004-08-68 CONFIDENTIAL NEED TO KNOW
Files in the /etc/security and /etc/default directories contain security values. For more information, see Chapter 3, Controlling Access to Systems (Tasks), in Oracle Solaris 11.1 Administration: Security Services.
Caution - Relax system security defaults only if site security policy allows you to.
Before You Begin
You are in the global zone and are assigned the solaris.admin.edit/filename authorization. By default, the root role has this authorization.
The following table lists the security files and which security values you might change in the files. The first two files are unique to Trusted Extensions.