This chapter covers how to configure Solaris Trusted Extensions on a system with a monitor. To work properly, Trusted Extensions software requires configuration of the following: labels, zones, the network, roles, and tools.Setting Up the Global Zone in Trusted Extensions Creating Labeled Zones Creating Roles and Users in Trusted Extensions Creating Home Directories in Trusted Extensions Adding Users and Hosts to an Existing Trusted Network Troubleshooting Your Trusted Extensions Configuration Additional Trusted Extensions Configuration Tasks For other configuration tasks, see Solaris Trusted Extensions Administrator’s Procedures. Before setting up the global zone, you must make decisions about your configuration. For the decisions, see Collecting Information and Making Decisions Before Installing Trusted Extensions.Task Description For Instructions Protect the hardware. Hardware can be protected by requiring a password to change hardware settings. Controlling Access to System Hardware in System Administration Guide: Security Services Configure labels. Labels must be configured for your site. If you plan to use the default label_encodings file, you can skip this step. Check and Install Your Label Encodings File For IPv6, modify the /etc/system file. If you are running an IPv6 network, you modify the /etc/system file to enable IP to recognize labeled packets. Enable IPv6 Networking in Trusted Extensions Create space for a Solaris ZFS snapshot. If you plan to use a Solaris ZFS snapshot to clone zones, create the ZFS pool. ZFS is derived from and an acronym for “zettabyte file system”.Perform this task if you are going to clone the first zone to create the rest of the labeled zones. Create ZFS Pool for Cloning Zones Reboot and log in. Upon login, you are in the global zone, which is an environment that recognizes and enforces mandatory access control (MAC). Reboot and Log In to Trusted Extensions Initialize the Solaris Management Console. Trusted Extensions adds tools to the Solaris Management Console for administering users, roles, zones, and the network. Initialize the Solaris Management Console Server in Trusted Extensions Configure LDAP. If you are using the LDAP naming service, set up the LDAP service. Chapter 5, Configuring LDAP for Trusted Extensions (Tasks) If you have set up the LDAP service, make this system an LDAP client. Make the Global Zone an LDAP Client in Trusted Extensions Your encodings file must be compatible with any Trusted Extensions host with which you are communicating.Trusted Extensions installs a default label_encodings file. This default file is useful for demonstrations. However, this file might not be a good choice for your use. If you plan to use the default file, you can skip this procedure. If you are familiar with encodings files, you can use the following procedure. If you are not familiar with encodings files, consult Solaris Trusted Extensions Label Administration for requirements, procedures, and examples. You must successfully install labels before continuing, or the configuration will fail. As the security administrator, you have just added the Trusted Extensions packages, so you are already logged in.The security administrator is responsible for editing, checking, and maintaining the label_encodings file. If you plan to edit the label_encodings file, make sure that the file itself is writable. For more information, see the label_encodings4 man page. Insert the media with the label_encodings file into the appropriate device. Copy the label_encodings file to the disk. Check the syntax of the new label encodings file.Open the Trusted_Extensions folder.Click mouse button 3 on the background. From the Workspace menu, choose Applications → Application Manager. Double-click the Trusted_Extensions folder icon. Illustration shows the Trusted_Extensions folder icon. Double-click the Check Encodings action.In the dialog box, type the full path name to the file:/full-pathname-of-label-encodings-fileThe chk_encodings command is invoked to check the syntax of the file. The results are displayed in the Check Encodings dialog box. Read the contents of the Check Encodings dialog box. Do one of the following:CONTINUEIf the Check Encodings action reports no errors, you can continue. Go to Step 7. RESOLVE ERRORSIf the Check Encodings action reports errors, the errors must be resolved before continuing. For assistance, see Chapter 3, Making a Label Encodings File (Tasks), in Solaris Trusted Extensions Label Administration. If the file passes the syntax check, click Yes.The Check Encodings action creates a backup copy of the original file, then installs the checked version in /etc/security/tsol/label_encodings. The action then restarts the label daemon.Your label encodings file must pass the Check Encodings test before you continue. In this example, the administrator tests several label_encodings files by using the command line.# /usr/sbin/chk_encodings /var/encodings/label_encodings1 No errors found in /var/encodings/label_encodings1 # /usr/sbin/chk_encodings /var/encodings/label_encodings2 No errors found in /var/encodings/label_encodings2When management decides to use the label_encodings2 file, the administrator runs a semantic analysis of the file.# /usr/sbin/chk_encodings -a /var/encodings/label_encodings2 No errors found in /var/encodings/label_encodings2 ---> VERSION = MYCOMPANY LABEL ENCODINGS 2.0 10/10/2006 ---> CLASSIFICATIONS <--- Classification 1: PUBLIC Initial Compartment bits: 10 Initial Markings bits: NONE ---> COMPARTENTS AND MARKINGS USAGE ANALYSIS <--- ... ---> SENSITIVITY LABEL to COLOR MAPPING <--- ...The administrator prints a copy of the semantic analysis for her records, then moves the file to the /etc/security/tsol directory.# cp /var/encodings/label_encodings2 /etc/security/tsol/label.encodings.10.10.06 # cd /etc/security/tsol # cp label_encodings label_encodings.tx.orig # cp label.encodings.10.10.06 label_encodingsFinally, the administrator verifies that the label_encodings file is the company file.# /usr/sbin/chk_encodings -a /etc/security/tsol/label_encodings | head -4 No errors found in /etc/security/tsol/label_encodings ---> VERSION = MYCOMPANY LABEL ENCODINGS 2.0 10/10/2006 When IPv6 is disabled, Trusted Extensions cannot forward IPv6 packets with CIPSO options. To enable an IPv6 network in Trusted Extensions, you must add an entry in the /etc/system file. Type the following entry into the /etc/system file:set ip:ip6opt_ls = 0x0a If error messages during boot indicate that your IPv6 configuration is incorrect, correct the entry:Check that the entry is spelled correctly. Check that the system has been rebooted after adding the correct entry to the /etc/system file. If you install Trusted Extensions on a Solaris system that currently has IPv6 enabled, but you fail to add the IP entry in /etc/system, you see the following error message: t_optmgmt: System error: Cannot assign requested address time-stamp If you install Trusted Extensions on a Solaris system that does not have IPv6 enabled, and you fail to add the IP entry in /etc/system, you see the following types of error messages:WARNING: IPv6 not enabled via /etc/system Failed to configure IPv6 interface(s): hme0 rpcbind: Unable to join IPv6 multicast group for rpc broadcast broadcast-number If you plan to use a Solaris ZFS snapshot as your zone template, you need to create a ZFS pool from a ZFS file or a ZFS device. This pool holds the snapshot for cloning each zone. You use the /zone device for your ZFS pool. You have set aside disk space during Solaris installation for a ZFS file system. For details, see Planning for Zones in Trusted Extensions. Unmount the /zone partition.During installation, you created a /zone partition with sufficient disk space of about 2000 MBytes.# umount /zone Remove the /zone mount point.# rmdir /zone Comment out the /zone entry in the vfstab file.Prevent the /zone entry from being read.Open the vfstab file in an editor. Prefix the /zone entry with a comment sign.#/dev/dsk/cntndnsn /dev/dsk/cntndnsn /zone ufs 2 yes - Copy the disk slice, cntndnsn, to the clipboard. Save the file, and close the editor. Use the disk slice to re-create /zone as a ZFS pool.# zpool create -f zone cntndnsnFor example, if your /zone entry used disk slice c0t0d0s5, then the command would be the following:# zpool create -f zone c0t0d0s5 Verify that the ZFS pool is healthy.Use one of the following commands:# zpool status -x zone pool 'zone' is healthy# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT /zone 5.84G 80K 5.84G 7% ONLINE -In this example, the install team reserved a 6000MByte partition for zones. For more information, see the zpool1M man page. At most sites, two or more administrators, who serve as an install team, are present when configuring the system. Before you first log in, become familiar with the desktop and label options in Trusted Extensions. For details, see Chapter 2, Logging In to Trusted Extensions (Tasks), in Solaris Trusted Extensions User’s Guide. Reboot the system.# /usr/sbin/rebootIf your system does not have a graphical display, go to Chapter 6, Configuring a Headless System With Trusted Extensions (Tasks). Log in to the Solaris Trusted Extensions (CDE) desktop as superuser.In the login window, select Solaris Trusted Extensions (CDE) as the desktop.This Trusted CDE desktop contains actions that are useful when configuring the system. In the login dialog box, type root and the root password.Users must not disclose their passwords to another person, as that person might then have access to the data of the user and will not be uniquely identified or accountable. Note that disclosure can be direct, through the user deliberately disclosing his/her password to another person, or indirect, such as through writing it down, or choosing an insecure password. Trusted Extensions software provides protection against insecure passwords, but cannot prevent a user disclosing his/her password or writing it down. Read the information in the Last Login dialog box. Illustration shows the Last Login dialog box. Then click OK to dismiss the box. Read the Label Builder.Click OK to accept the default label.Once the login process is complete, the Trusted Extensions screen appears briefly, and you are in a desktop session with four workspaces. The Trusted Path symbol is displayed in the trusted stripe. You must log off or lock the screen before leaving a system unattended. Otherwise, a person can access the system without having to pass identification and authentication, and that person would not be uniquely identified or accountable. This procedure enables you to administer users, roles, hosts, zones, and the network on this system. On the first system that you configure, only the files scope is available. You must be superuser. Start the Solaris Management Console.# /usr/sbin/smc &The first time the Solaris Management Console is started, it performs several registration tasks. These tasks can take a few minutes. Do one of the following if toolbox icons do not appear in the Solaris Management Console:If the Navigation pane is not visible:In the Open Toolbox dialog box that is displayed, click Load next to this system's name under Server.If this system does not have the recommended amount of memory and swap, it might take a few minutes for the toolboxes to display. For recommendations, see Installing or Upgrading the Solaris OS for Trusted Extensions. From the list of toolboxes, select a toolbox whose Policy=TSOL.Figure 4–1 shows a This Computer (this-host: Scope=Files, Policy=TSOL) toolbox. Trusted Extensions modifies tools under the System Configuration node.Do not choose a toolbox that has no policy. Toolboxes without a listed policy do not support Trusted Extensions. Your toolbox choice depends on which scope you want to influence. To edit local files, choose the Files scope. To edit LDAP databases, choose the LDAP scope.After you complete Edit the LDAP Toolbox in the Solaris Management Console, the LDAP scope is available. Click Open. If the Navigation pane is visible, but the toolbox icons are stop signs:Exit the Solaris Management Console. Restart the Solaris Management Console.# /usr/sbin/smc & If you have not yet done so, select a toolbox whose Policy=TSOL.The following figure shows a This Computer (this-host: Scope=Files, Policy=TSOL) toolbox. Trusted Extensions modifies tools under the System Configuration node.

Window shows the System Configuration node with the Users tools and the Computers and Networks tools.

Save the current toolbox.Saving a Policy=TSOL toolbox enables a Trusted Extensions toolbox to load by default. Preferences are saved per role, per host. The host is the Solaris Management Console server.From the Console menu, choose Preferences.The Home toolbox is selected. Define a Policy=TSOL toolbox as the Home toolbox.Put the current toolbox in the Location field by clicking the Use Current Toolbox button. Click OK to save the preferences. Exit the Solaris Management Console. For an overview of the Trusted Extensions additions to the Solaris Management Console, see Solaris Management Console Tools in Solaris Trusted Extensions Administrator’s Procedures. To use the Solaris Management Console to create security templates, see Configuring Trusted Network Databases (Task Map) in Solaris Trusted Extensions Administrator’s Procedures. For LDAP, this procedure establishes the naming service configuration for the global zone. If you are not using LDAP, you can skip this procedure. The Sun Java System Directory Server, that is, the LDAP server, must exist. The server must be populated with Trusted Extensions databases, and this system must be able to contact the server. So, the system that you are configuring must have an entry in the tnrhdb database on the LDAP server, or this system must be included in a wildcard entry before you perform this procedure.If an LDAP server that is configured with Trusted Extensions does not exist, you must complete the procedures in Chapter 5, Configuring LDAP for Trusted Extensions (Tasks) before you perform this procedure. Save a copy of the original nsswitch.ldap file.The standard naming service switch file for LDAP is too restrictive for Trusted Extensions.# cd /etc # cp nsswitch.ldap nsswitch.ldap.orig If you are using DNS, change the nsswitch.ldap file entries for the following services.The correct entries are similar to the following:hosts: files dns ldap ipnodes: files dns ldap networks: ldap files protocols: ldap files rpc: ldap files ethers: ldap files netmasks: ldap files bootparams: ldap files publickey: ldap files services: filesNote that Trusted Extensions adds two entries:tnrhtp: files ldap tnrhdb: files ldap Copy the modified nsswitch.ldap file to nsswitch.conf.# cp nsswitch.ldap nsswitch.conf In a Trusted CDE workspace, navigate to the Trusted_Extensions folder.Click mouse button 3 on the background. From the Workspace menu, choose Applications → Application Manager. Double-click the Trusted_Extensions folder icon.This folder contains actions that set up interfaces, LDAP clients, and labeled zones. Double-click the Create LDAP Client action.Answer the following prompts:Domain Name: Type the domain name Hostname of LDAP Server: Type the name of the server IP Address of LDAP Server: Type the IP address LDAP Proxy Password: Type the password to the server Profile Name: Type the profile name Click OK.The following completion message appears:global zone will be LDAP client of LDAP-server System successfully configured. *** Select Close or Exit from the window menu to close this window *** Close the action window. Verify that the information on the server is correct.Open a terminal window, and query the LDAP server.# ldapclient listThe output looks similar to the following:NS_LDAP_FILE_VERSION= 2.0 NS_LDAP_BINDDN= cn=proxyagent,ou=profile,dc=domain-name ... NS_LDAP_BIND_TIME= number Correct any errors.If you get an error, run the Create LDAP Client action with the correct values. For example, the following error can indicate that the system does not have an entry on the LDAP server:LDAP ERROR (91): Can't connect to the LDAP server. Failed to find defaultSearchBase for domain domain-nameTo correct this error, you need to check the LDAP server. The txzonemgr script steps you through all the following tasks that configure labeled zones.You must be running the Solaris 10 8/07 release of Trusted Extensions to use the txzonemgr procedures. Or, you must install all patches for this release. The instructions in this section configure labeled zones on a system that has been assigned at most two IP addresses. For other configurations, see the configuration options in Task Map: Preparing For and Installing Trusted Extensions.Task Description For Instructions 1. Run the txzonemgr script. The txzonemgr script creates a GUI that presents the appropriate tasks as you configure your zones. Run the txzonemgr Script 2. Manage network interfaces in the global zone. Configure interfaces in the global zone, or create logical interfaces and configure them in the global zone. Configure the Network Interfaces in Trusted Extensions 3. Name and label the zone. Name the zone with a version of its label, and assign the label. Name and Label the Zone 4. Install and boot the zone. Install the packages in the zone. Configure services in the zone. A Zone Terminal Console enables you to view the activity in the zone. Install the Labeled ZoneBoot the Labeled Zone 5. Verify the status of the zone. Verify that the labeled zone is running, and that the zone can communicate with the global zone. Verify the Status of the Zone 6. Customize the zone. Remove unwanted services from the zone.If the zone is going to be used to create other zones, remove information that is specific to this zone only. Customize the Labeled Zone 7. Create the rest of the zones. Use the method that you have chosen to create your second zone. For a discussion of zone creation methods, see Planning for Zones in Trusted Extensions. Create Another Zone in Trusted Extensions 8. (Optional) Add zone-specific network interfaces. To effect network isolation, add one or more network interfaces to a labeled zone. Typically, this configuration is used to isolate labeled subnets. Add a Network Interface to an Existing Labeled Zone This script steps you through the tasks to properly configure, install, initialize, and boot labeled zones. In the script, you name each zone, associate the name with a label, install the packages to create a virtual OS, and then boot the zone to start services in that zone. The script includes copy zone and clone zone tasks. You can also halt a zone, change the state of a zone, and add zone-specific network interfaces.This script presents a dynamically-determined menu that displays only valid choices for the current circumstances. For instance, if the status of a zone is configured, the Install zone menu item is not displayed. Tasks that are completed do not display in the list. You are superuser.If you plan to clone zones, you have completed the preparation for cloning zones. If you plan to use your own security templates, you have created the templates. Open a terminal window in the global zone. Run the txzonemgr script.# /usr/sbin/txzonemgrThe script opens the Labeled Zone Manager dialog box. This zenity dialog box prompts you for the appropriate tasks, depending on the current state of your installation.To perform a task, you select the menu item, then press the Return key or click OK. When you are prompted for text, type the text then press the Return key or click OK. If you are configuring your system to use DHCP or to prevent networks from contacting the global zone, refer to the laptop instructions in the Trusted Extensions section of OpenSolaris Community: Security web page. In this task, you configure the networking in the global zone. You must create exactly one all-zones interface. An all-zones interface is shared by the labeled zones and the global zone. The shared interface is used to route traffic between the labeled zones and the global zone. To configure this interface, do one of the following:Create a logical interface from a physical interface, then share the physical interface.This configuration is the simplest to administer. Choose this configuration when your system has been assigned two IP addresses. In this procedure, the logical interface becomes the global zone's specific address, and the physical interface is shared between the global zone and the labeled zones. Share a physical interfaceChoose this configuration when your system has been assigned one IP address. In this configuration, the physical interface is shared between the global zone and the labeled zones. Share a virtual network interface, vni0Choose this configuration when you are configuring DHCP, or when each subnetwork is at a different label. For a sample procedure, refer to the laptop instructions in the Trusted Extensions section of OpenSolaris Community: Security web page. To add zone-specific network interfaces, finish and verify zone creation before adding the interfaces. For the procedure, see Add a Network Interface to an Existing Labeled Zone. You are superuser in the global zone.The Labeled Zone Manager is displayed. To open this GUI, see Run the txzonemgr Script. In the Labeled Zone Manager, select Manage Network Interfaces and click OK.A list of interfaces is displayed.In this example, the physical interface was assigned a host name and an IP address during installation. Select the physical interface.A system with one interface displays a menu similar to the following. The annotation is added for assistance:vni0 DownVirtual Network Interface eri0 global 10.10.9.9 cipso Up Physical InterfaceSelect the eri0 interface. Click OK Select the appropriate task for this network interface.You are offered three options:View Template Assign a label to the interface Share Enable the global zone and labeled zones to use this interface Create Logical Interface Create an interface to use for sharingIf your system has one IP address, go to Step 4. If your system has two IP addresses, go to Step 6. On a system with one IP address, share the physical interface.In this configuration, the host's IP address applies to all zones. Therefore, the host's address is the all-zones address. This host cannot be used as a multilevel server. For example, users cannot share files from this system. The system cannot be an LDAP proxy server, an NFS home directory server, or a print server.Select Share and click OK. At the prompt, accept the host name. Dismiss the dialog box that displays the netmask.eri0 all-zones 10.10.9.8 cipso Up Skip the next step.You are successful when the physical interface is an all-zones interface. On a system with two IP addresses, create a logical interface.Then, share the physical interface.This is the simplest Trusted Extensions network configuration. In this configuration, the main IP address can be used by other systems to reach any zone on this system, and the logical interface is zone-specific to the global zone. The global zone can be used as a multilevel server.Select Create Logical Interface and click OK.Dismiss the dialog box that confirms the creation of a new logical interface. Select Set IP address and click OK. At the prompt, specify the host name for the logical interface and click OK.For example, specify machine1-services as the host name for the logical interface. The name indicates that this host offers multilevel services. At the prompt, specify the IP address for the logical interface and click OK.For example, specify 10.10.9.2 as the IP address for the logical interface. Select the logical interface again and click OK. Select Bring Up and click OK.The interface is displayed as Up.eri0 global 10.10.9.1 cipso Up eri0:1 global 10.10.9.2 cipso Up Share the physical interface.Select the physical interface and click OK. Select Share and click OK.eri0 all-zones 10.10.9.1 cipso Up eri0:1 global 10.10.9.2 cipso Up You are successful when at least one interface is an all-zones interface. On a system where the global zone has a unique interface and labeled zones share a second interface with the global zone, the /etc/hosts file appears similar to the following:# cat /etc/hosts ... 127.0.0.1 localhost 192.168.0.11 machine1 loghost 192.168.0.12 machine1-services In the default configuration, the tnrhdb file appears similar to the following:# cat /etc/security/tsol/tnrhdb ... 127.0.0.1:cipso 192.168.0.11:cipso 192.168.0.12:cipso 0.0.0.0:admin_lowIf the all-zones interface is not in the tnrhdb file, the interface defaults to cipso. In this example, the administrator is not planning to use the system as a multilevel server. To conserve IP addresses, the global zone is configured to share its IP address with every labeled zone.The administrator selects Share for the hme0 interface on the system. The software configures all zones to have logical NICs. These logical NICs share a single physical NIC in the global zone.The administrator runs the ifconfig -a command to verify that the physical interface hme0 on network interface 192.168.0.11 is shared. The value all-zones is displayed: lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 hme0: flags=1000843<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 all-zones inet 192.168.0.11 netmask fffffe00 broadcast 192.168.0.255The administrator also examines the contents of the /etc/hostname.hme0 file:192.168.0.11 all-zones You do not have to create a zone for every label in your label_encodings file, but you can. The administrative GUIs enumerate the labels that can have zones created for them on this system. You are superuser in the global zone. The Labeled Zone Manager dialog box is displayed. To open this GUI, see Run the txzonemgr Script. You have configured the network interfaces in the global zone.You have created any security templates that you need. A security template defines, among other attributes, the label range that can be assigned to a network interface. The default security templates might satisfy your needs.For an overview of security templates, see Network Security Attributes in Trusted Extensions in Solaris Trusted Extensions Administrator’s Procedures. To use the Solaris Management Console to create security templates, see Configuring Trusted Network Databases (Task Map) in Solaris Trusted Extensions Administrator’s Procedures. In the Labeled Zone Manager, select Create a new zone and click OK.You are prompted for a name.Type the name for the zone.Give the zone a name that is similar to the zone's label. For example, the name of a zone whose label is CONFIDENTIAL: RESTRICTED would be restricted. For example, the default label_encodings file contains the following labels:PUBLIC CONFIDENTIAL: INTERNAL USE ONLY CONFIDENTIAL: NEED TO KNOW CONFIDENTIAL: RESTRICTED SANDBOX: PLAYGROUND MAX LABELAlthough you could create one zone per label, consider creating the following zones:On a system for all users, create one zone for the PUBLIC label and three zones for the CONFIDENTIAL labels. On a system for developers, create a zone for the SANDBOX: PLAYGROUND label. Because SANDBOX: PLAYGROUND is defined as a disjoint label for developers, only systems that developers use need a zone for this label. Do not create a zone for the MAX LABEL label, which is defined to be a clearance. Click OK.The dialog box displays zone-name:configured above a list of tasks. To label the zone, choose one of the following:If you are using a customized label_encodings file, label the zone by using the Trusted Network Zones tool.Open the Trusted Network Zones tool in the Solaris Management Console.Start the Solaris Management Console.# /usr/sbin/smc & Open the Trusted Extensions toolbox for the local system.Choose Console → Open Toolbox. Select the toolbox that is named This Computer (this-host: Scope=Files, Policy=TSOL). Click Open. Under System Configuration, navigate to Computers and Networks.Provide a password when prompted. Double-click the Trusted Network Zones tool. For each zone, associate the appropriate label with the zone name.Choose Action → Add Zone Configuration.The dialog box displays the name of a zone that does not have an assigned label. Look at the zone name, then click Edit. In the Label Builder, click the appropriate label for the zone name.If you click the wrong label, click the label again to deselect it, then click the correct label. Save the assignment.Click OK in the Label Builder, then click OK in the Trusted Network Zones Properties dialog box. You are finished when every zone that you want is listed in the panel, or the Add Zone Configuration menu item opens a dialog box that does not have a value for Zone Name. If you are using the default label_encodings file, use the Labeled Zone Manager.Click Select Label menu item and OK to display the list of available labels.Select the label for the zone.For a zone that is named public, you would select the label PUBLIC from the list. Click OK.A list of tasks is displayed. You are superuser in the global zone. The zone is installed, and has an assigned a network interface. The Labeled Zone Manager dialog box is displayed with the subtitle zone-name:configured. To open this GUI, see Run the txzonemgr Script. From the Labeled Zone Manager, select Install and click OK.This process takes some time to finish. Do not perform other tasks while this task is completing. The system copies packages from the global zone to the non-global zone. This task installs a labeled virtual operating system in the zone. To continue the example, this task installs the public zone. The GUI displays output similar to the following.# Labeled Zone Manager: Installing zone-name zone Preparing to install zone <zonename> Creating list of files to copy from the global zone Copying <total> files to the zone Initializing zone product registry Determining zone package initialization order. Preparing to initialize <subtotal> packages on the zone. Initializing package <number> of <subtotal>: percent complete: percent Initialized <subtotal> packages on zone. Zone <zonename> is initialized. The file /zone/internal/root/var/sadm/system/logs/install_log contains a log of the zone installation.When the installation is complete, you are prompted for the name of the host. A name is supplied. Accept the name of the host.The dialog box displays zone-name:installed above a list of tasks. If warnings that are similar to the following are displayed: Installation of these packages generated errors: SUNWpkgname, read the install log and finish installing the packages. You are superuser in the global zone. The zone is installed, and has an assigned a network interface. The Labeled Zone Manager dialog box is displayed with the subtitle zone-name:installed. To open this GUI, see Run the txzonemgr Script. In the Labeled Zone manager, select Zone Console and click OK.A separate console window appears for the current labeled zone. Select Boot.The Zone Terminal Console tracks the progress of booting the zone. If the zone is created from scratch, messages that are similar to the following appear in the console:[Connected to zone 'public' console] [NOTICE: Zone booting up] ... Hostname: zone-name Loading smf(5) service descriptions: number/total Creating new rsa public/private host key pair Creating new dsa public/private host key pair rebooting system due to change(s) in /etc/default/init [NOTICE: Zone rebooting]Do not perform other tasks while this task is completing. Sometimes, error messages are displayed and the zone does not reboot. In the Zone Terminal Console, press the Return key. If you are prompted to type y to reboot, type y and press the Return key. The zone reboots. If this zone was copied or cloned from another zone, continue with Verify the Status of the Zone.If this zone is the first zone, continue with Customize the Labeled Zone. The X server runs in the global zone. Each labeled zone must be able to connect with the global zone to use the X server. Therefore, zone networking must work before a zone can be used. For background information, see Planning for Multilevel Access. Verify that the zone has been completely started.In the zone-name: Zone Terminal Console, log in as root.hostname console login: root Password: Type root password In the Zone Terminal Console, verify that critical services are running.# svcs -xv svc:/application/print/server:default (LP print server) State: disabled since Tue Oct 10 10:10:10 2006 Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: lpsched(1M) ...The sendmail and print services are not critical services. Verify that the zone has a valid IP address.# ifconfig -aFor example, the following output shows an IP address for the hme0 interface.# ... hme0: flags=1000843<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 all-zones inet 192.168.0.11 netmask fffffe00 broadcast 192.168.0.255 Verify that the zone can communicate with the global zone.Set the DISPLAY variable to point to the X server# DISPLAY=global-zone-hostname:n.n # export DISPLAY From the terminal window, display a GUI.For example, display a clock.# /usr/openwin/bin/xclockIf the clock at the label of the zone does not appear, the zone networking has not been configured correctly. For debugging suggestions, see Labeled Zone Is Unable to Access the X Server. Close the GUI before continuing. From the global zone, check the status of the labeled zones.# zoneadm list -v ID NAME STATUS PATH BRAND IP 0 global running / native shared 3 internal running /zone/internal native shared 4 needtoknow running /zone/needtoknow native shared 5 restricted running /zone/restricted native shared If you are going to clone zones or copy zones, this procedure configures a zone to be a template for other zones. In addition, this procedure configures a zone that has not been created from a template for use. You are superuser in the global zone. You have completed Verify the Status of the Zone. In the Zone Terminal Console, disable services that are unnecessary in a labeled zone.If you are copying or cloning this zone, the services that you disable are disabled in the new zones. The services that are online on your system depend on the service manifest for the zone. Use the netservices limited command to turn off services that labeled zones do not need.Remove many unnecessary services.# netservices limited List the remaining services.# svcs ... STATE STIME FMRI online 13:05:00 svc:/application/graphical-login/cde-login:default ... Disable graphical login.# svcadm disable svc:/application/graphical-login/cde-login # svcs cde-login STATE STIME FMRI disabled 13:06:22 svc:/application/graphical-login/cde-login:default For information about the service management framework, see the smf5 man page. In the Labeled Zone Manager, select Halt to halt the zone. Before continuing, verify that the zone is shut down.In the zone-name: Zone Terminal Console, the following message indicates that the zone is shut down.[ NOTICE: Zone halted]If you are not copying or cloning this zone, create the remaining zones in the way that you created this first zone. Otherwise, continue with the next step. If you are using this zone as a template for other zones, do the following:Remove the auto_home_zone-name file.In a terminal window in the global zone, remove this file from the zone-name zone.# cd /zone/zone-name/root/etc # ls auto_home* auto_home auto_home_zone-name # rm auto_home_zone-nameFor example, if the public zone is the template for cloning other zones, remove the auto_home_public file:# cd /zone/public/root/etc # rm auto_home_public If you plan to clone this zone, create the ZFS snapshot in the next step, then continue with Create Another Zone in Trusted Extensions. If you plan to copy this zone, complete Step 6, then continue with Create Another Zone in Trusted Extensions. To create a zone template for cloning the remaining zones, select Create Snapshot and click OK.The zone for the snapshot must be in a ZFS file system. You created a ZFS file system for the zone in Create ZFS Pool for Cloning Zones. To verify that the customized zone is still usable, select Boot from the Labeled Zone Manager.The Zone Terminal Console tracks the progress of booting the zone. Messages that are similar to the following appear in the console:[Connected to zone 'public' console] [NOTICE: Zone booting up] ... Hostname: zonenamePress the Return key for a login prompt. You can log in as root. You have three options:You can copy the first zone. You can repeat the steps that you used to create the first zone. You can clone the first zone. You have completed Customize the Labeled Zone.The Labeled Zone Manager dialog box is displayed. To open this GUI, see Run the txzonemgr Script. Name and label the zone.For details, see Name and Label the Zone. Continue with your zone creation strategy by choosing one of the following methods: You will repeat these steps for every new zone.Create every zone from scratch.Complete Install the Labeled Zone. Complete Boot the Labeled Zone. Complete Verify the Status of the Zone. Complete Customize the Labeled Zone. Copy the zone that you just labeled.In the Labeled Zone Manager, select Copy and click OK. Select the zone template and click OK.A window displays the copying process. When the process completes, the zone is installed.If the Labeled Zone Manager displays zone-name:configured, continue with the next step. Otherwise, continue with Step e. Select the menu item Select another zone, and click OK. Select the newly installed zone and click OK. Complete Boot the Labeled Zone. Complete Verify the Status of the Zone. Clone the zone that you just labeled.In the Labeled Zone Manager, select Clone and click OK. Select a ZFS snapshot from the list and click OK.For example, if you created a snapshot from public, select the zone/public@snapshot.When the cloning process completes, the zone is installed. If the Labeled Zone Manager displays zone-name:configured, continue with the next step. Otherwise, continue with Step e. Select the menu item Select another zone, and click OK. Select the newly installed zone and click OK. Complete Boot the Labeled Zone. Complete Verify the Status of the Zone. When you have completed Verify the Status of the Zone for every zone, and you want each zone to be on a separate physical network, continue with Add a Network Interface to an Existing Labeled Zone. If you have not yet created roles, continue with Creating Roles and Users in Trusted Extensions. If you have already created roles, continue with Creating Home Directories in Trusted Extensions. This procedure adds zone-specific network interfaces to existing labeled zones. This configuration supports environments where each zone is connected to a separate physical network.The global zone must configure an IP address for every subnet in which a non-global zone address is configured. You are superuser in the global zone. You have successfully completed Verify the Status of the Zone. In the global zone, type the IP addresses and hostnames for the additional network interfaces into the /etc/hosts file.Use a standard naming convention, such as adding -zone-name to the name of the host.## /etc/hosts in global zone 10.10.8.2 hostname-zone-name1 10.10.8.3 hostname-global-name1 10.10.9.2 hostname-zone-name2 10.10.9.3 hostname-global-name2 For the network for each interface, add entries to the /etc/netmasks file.## /etc/netmasks in global zone 10.10.8.0 255.255.255.0 10.10.9.0 255.255.255.0For more information, see the netmasks4 man page. In the global zone, plumb the zone-specific physical interfaces.Identify the physical interfaces that are already plumbed.# ifconfig -a Configure the global zone addresses on each interface.# ifconfig interface-nameN1 plumb # ifconfig interface-nameN1 10.10.8.3 up # ifconfig interface-nameN2 plumb # ifconfig interface-nameN2 10.10.9.3 up For each global zone address, create a hostname.interface-nameN file.# /etc/hostname.interface-nameN1 10.10.8.3 # /etc/hostname.interface-nameN2 10.10.9.3 The global zone addresses are configured immediately upon system startup. The zone-specific addresses are configured when the zone is booted. Assign a security template to each zone-specific network interface.If the gateway to the network is not configured with labels, assign the admin_low security template. If the gateway to the network is labeled, assign a cipso security template. You can create security templates of host type cipso that reflect the label of every network. For the procedures to create and assign the templates, see Configuring Trusted Network Databases (Task Map) in Solaris Trusted Extensions Administrator’s Procedures. Halt every labeled zone to which you plan to add a zone-specific interface.# zoneadm -z zone-name halt Start the Labeled Zone Manager.# /usr/sbin/txzonemgr For each zone where you want to add a zone-specific interface, do the following:Select the zone. Select Add Network. Name the network interface. Type the IP address of the interface. In the Labeled Zone Manager for every completed zone, select Zone Console. Select Boot. In the Zone Console, verify that the interfaces have been created.# ifconfig -a Verify that the zone has a route to the gateway for the subnet.# netstat -rn To debug zone configuration, see the following:Chapter 28, Troubleshooting Miscellaneous Solaris Zones Problems, in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones Troubleshooting Your Trusted Extensions Configuration Troubleshooting the Trusted Network (Task Map) in Solaris Trusted Extensions Administrator’s Procedures If you are already using administrative roles, you might want to add a Security Administrator role. For sites that have not yet implemented roles, the procedure for creating them is similar to the procedure in the Solaris OS. Trusted Extensions adds the Security Administrator role and requires the use of the Solaris Management Console to administer a Trusted Extensions domain.Role creation in Trusted Extensions is identical to role creation in the Solaris OS. However, in Trusted Extensions, a Security Administrator role is required. To create a local Security Administrator role, you can also use the command-line interface, as in Example 4–4. You must be superuser, in the root role, or in the Primary Administrator role.To create the role on the network, you must have completed Configuring the Solaris Management Console for LDAP (Task Map). Start the Solaris Management Console.# /usr/sbin/smc & Select the appropriate toolbox.To create the role locally, use This Computer (this-host: Scope=Files, Policy=TSOL). To create the role in the LDAP service, use This Computer (this-host: Scope=LDAP, Policy=TSOL). Click System Configuration, then click Users.You are prompted for your password. Type the appropriate password. Double-click Administrative Roles. From the Action menu, choose Add Administrative Role. Create the Security Administrator role.Use the following information as a guide:Role name – secadmin Full name – Security Administrator Description – Site Security Officer No proprietary information here. Role ID Number – ≥100 Role shell – Administrator's Bourne (profile shell) Create a role mailing list – Leave the checkbox selected. Password and confirm – Assign a password of at least 6 alphanumeric characters.The password for the Security Administrator role, and all passwords, must be difficult to guess, thus reducing the chance of an adversary gaining unauthorized access by attempting to guess passwords.For all administrative roles, make the account Always Available, and do not set password expiration dates. Available and Granted Rights – Information Security, User Security Home Directory Server – home-directory-server Home Directory Path – /mount-path Assign Users– This field is automatically filled in when you assign a role to a user. After creating the role, check that the settings are correct.Select the role, then double-click it.Review the values in the following fields:Available Groups – Add groups if required. Trusted Extensions Attributes – Defaults are correct.For a single-label system where the labels must not be visible, choose Hide for Label: Show or Hide. Audit Excluded and Included – Set audit flags only if the role's audit flags are exceptions to the system settings in the audit_control file. To create other roles, use the Security Administrator role as a guide.For examples, see How to Create and Assign a Role By Using the GUI in System Administration Guide: Security Services. Give each role a unique ID, and assign to the role the correct rights profile. Possible roles include the following:admin Role – System Administrator Granted Rights primaryadmin Role – Primary Administrator Granted Rights oper Role – Operator Granted Rights In this example, the root user adds the Security Administrator role to the local system by using the roleadd command. For details, see the roleadd1M man page. The root user consults Table 1–2 before creating the role.# roleadd -c "Local Security Administrator" -d /export/home1 \ -u 110 -P "Information Security,User Security" -K lock_after_retries=no \ -K idletime=5 -K idlecmd=lock -K labelview=showsl \ -K min_label=ADMIN_LOW -K clearance=ADMIN_HIGH secadminThe root user provides an initial password for the role.# passwd -r files secadmin New Password: <Type password> Re-enter new Password: <Retype password> passwd: password successfully changed for secadmin #To assign the role to a local user, see Example 4–5. To create a local user, you can use the command-line interface, as in Example 4–5, instead of the following procedure. Where site security policy permits, you can choose to create a user who can assume more than one administrative role.For secure user creation, the System Administrator role creates the user, and the Security Administrator role assigns security-relevant attributes, such as a password. You must be superuser, in the root role, in the Security Administrator role, or in the Primary Administrator role. The Security Administrator role has the least amount of privilege that is required for user creation.The Solaris Management Console is displayed. For details, see Create the Security Administrator Role in Trusted Extensions. Double-click User Accounts in the Solaris Management Console. From the Action menu, choose Add User → Use Wizard.The names and IDs of roles and users come from the same pool. Do not use existing names or IDs for the users that you add. Follow the online help.You can also follow the procedures in How to Add a User With the Solaris Management Console’s Users Tool in System Administration Guide: Basic Administration. After creating the user, double-click the created user to modify the settings.For users who can assume roles, make the user account Always Available, and do not set password expiration dates. Ensure that the following fields are correctly set:Description – No proprietary information here. Password and confirm – Assign a password of at least 6 alphanumeric characters.When the install team chooses a password, the team must select a password that is difficult to guess, thus reducing the chance of an adversary gaining unauthorized access by attempting to guess passwords. Account Availability – Always Available. Trusted Extensions Attributes – Defaults are correct.For a single-label system where the labels must not be visible, choose Hide for Label: Show or Hide. Account Usage – Set Idle time and Idle action.Lock account – Set to No for any user who can assume a role. Customize the user's environment.Assign Convenient AuthorizationsAfter checking your site security policy, you might want to grant your first users the Convenient Authorizations rights profile. With this right, users can allocate devices, print PostScript files, print without labels, remotely log in, and shut down the system. Customize user initialization filesSee Chapter 7, Managing Users, Rights, and Roles in Trusted Extensions (Tasks), in Solaris Trusted Extensions Administrator’s Procedures.Also see Managing Users and Rights With the Solaris Management Console (Task Map) in Solaris Trusted Extensions Administrator’s Procedures. Create multilabel copy and link filesOn a multilabel system, users and roles can be set up with files that list user initialization files to be copied or linked to other labels. For more information, see .copy_files and .link_files Files in Solaris Trusted Extensions Administrator’s Procedures. In this example, the root user creates a local user who can assume the Security Administrator role. For details, see the useradd1M and atohexlabel1M man pages.First, the root user determines the hexadecimal format of the user's minimum label and clearance label.# atohexlabel public 0x0002-08-08 # atohexlabel -c "confidential restricted" 0x0004-08-78Next, the root user consults Table 1–2, and then creates the user.# useradd -c "Local user for Security Admin" -d /export/home1 \ -K idletime=10 -K idlecmd=logout -K lock_after_retries=no -K min_label=0x0002-08-08 -K clearance=0x0004-08-78 -K labelview=showsl jandoeThen, the root user provides an initial password.# passwd -r files jandoe New Password: <Type password> Re-enter new Password: <Retype password> passwd: password successfully changed for jandoe #Finally, the root user adds the Security Administrator role to the user's definition. The role was created in Create the Security Administrator Role in Trusted Extensions.# usermod -R secadmin jandoe To verify each role, assume the role. Then, perform tasks that only that role can perform. If you have configured DNS or routing, you must reboot after you create the roles and before you verify that the roles work. For each role, log in as a user who can assume the role. Open the Trusted Path menu.In Trusted CDE, click the workspace switch area. In Trusted JDS, click the trusted symbol. Illustration shows the Trusted Path menu in CDE. From the menu, assume the role. In the role workspace, start the Solaris Management Console.$ /usr/sbin/smc & Select the appropriate scope for the role that you are testing. Click System Services, and navigate to Users.You are prompted for a password.Type the role password. Double-click User Accounts. Click a user.The System Administrator role should be able to modify fields under the General, Home Directory, and Group tabs. The Security Administrator role should be able to modify fields under all tabs. The Primary Administrator role should be able to modify fields under all tabs. When the host is rebooted, the association between the devices and the underlying storage must be re-established. You have created at least one labeled zone. That zone is not being used for cloning. Reboot the system. Log in as the root user. Restart the zones service.# svcs zones STATE STIME FMRI offline - svc:/system/zones:default# svcadm restart svc:/system/zones:default Log out.Regular users can now log in. Their session is in a labeled zone. In Trusted Extensions, users need access to their home directories at every label at which the users work. To make every home directory available to the user requires that you create a multilevel home directory server, run the automounter on the server, and export the home directories. On the client side, you can run scripts to find the home directory for every zone for each user, or you can have the user log in to the home directory server.You must be superuser, in the root role, or in the Primary Administrator role. Install and configure the home directory server with Trusted Extensions software.If you are cloning zones, make sure that you use a Solaris ZFS snapshot that has empty home directories. Because users require a home directory at every label that they they can log in to, create every zone that a user can log in to. For example, if you use the default label_encodings file, you would create a zone for the PUBLIC label. If you are using UFS and not Solaris ZFS, enable the NFS server to serve itself.In the global zone, modify the automount entry in the nsswitch.conf file.Use the trusted editor to edit the /etc/nsswitch.conf file. For the procedure, see How to Edit Administrative Files in Trusted Extensions in Solaris Trusted Extensions Administrator’s Procedures.automount: files In the global zone, run the automount command. For every labeled zone, follow the automount procedure in How to NFS Mount Files in a Labeled Zone in Solaris Trusted Extensions Administrator’s Procedures. Then, return to this procedure. Verify that the home directories have been created.Log out of the home directory server. As a regular user, log in to the home directory server. In the login zone, open a terminal. In the terminal window, verify that the user's home directory exists. Create workspaces for every zone that the user can work in. In each zone, open a terminal window to verify that the user's home directory exists. Log out of the home directory server. Users can initially log in to the home directory server to create a home directory that can be shared with other systems. To create a home directory at every label, each user must log in to the home directory server at every label.Alternatively, you, as administrator, can create a script to create a mount point for home directories on each user's home system before the user first logs in. The script creates mount points at every label at which the user is permitted to work. The home directory server for your Trusted Extensions domain is configured. Choose whether to allow direct login to the server, or whether to run a script.Enable users to log in directly to the home directory server.Instruct each user to log in to the home directory server.After successful login, the user must log out. Instruct each user to log in again, and this time, to choose a different login label.The user uses the label builder to choose a different login label. After successful login, the user must log out. Instruct each user to repeat the login process for every label that the user is permitted to use. Instruct the users to log in from their regular workstation.Their home directory for their default label is available. When a user changes the label of a session or adds a workspace at a different label, the user's home directory for that label is mounted. Write a script that creates a home directory mount point for every user, and run the script.#!/bin/sh # for zoneroot in `/usr/sbin/zoneadm list -p | cut -d ":" -f4` ; do if [ $zoneroot != / ]; then prefix=$zoneroot/root/export for j in `getent passwd|tr ' ' _` ; do uid=`echo $j|cut -d ":" -f3` if [ $uid -ge 100 ]; then gid=`echo $j|cut -d ":" -f4` homedir=`echo $j|cut -d ":" -f6` mkdir -m 711 -p $prefix$homedir chown $uid:$gid $prefix$homedir fi done fi doneFrom the global zone, run this script on the NFS server. Then, run this script on every multilevel desktop that the user is going to log in to. If you have users who are defined in NIS maps, you can add them to your network. To add hosts and labels to hosts, see the following procedures:To add a host, you use the Computers and Networks tool set in the Solaris Management Console. For details, see How to Add Hosts to the System’s Known Network in Solaris Trusted Extensions Administrator’s Procedures.When you add a host to the LDAP server, add all IP addresses that are associated with the host. All-zones addresses, including addresses for labeled zones, must be added to the LDAP server. To label a host, see How to Assign a Security Template to a Host or a Group of Hosts in Solaris Trusted Extensions Administrator’s Procedures. You must be superuser, in the root role, or in the Primary Administrator role. From the NIS database, gather the information that you need.Create a file from the user's entry in the aliases database.% ypcat -k aliases | grep login-name > aliases.name Create a file from the user's entry in the passwd database.% ypcat -k passwd | grep "Full Name" > passwd.name Create a file from the user's entry in the auto_home_ database.% ypcat -k auto_home | grep login-name > auto_home_label Reformat the information for LDAP and Trusted Extensions.Use the sed command to reformat the aliases entry.% sed 's/ /:/g' aliases.login-name > aliases Use the nawk command to reformat the passwd entry.% nawk -F: '{print $1":x:"$3":"$4":"$5":"$6":"$7}' passwd.name > passwd Use the nawk command to create a shadow entry.% nawk -F: '{print $1":"$2":6445::::::"}' passwd.name > shadow Use the nawk command to create a user_attr entry.% nawk -F: '{print $1"::::lock_after_retries=yes-or-no;profiles=user-profile, ...; labelview=int-or-ext,show-or-hide;min_label=min-label; clearance=max-label;type=normal;roles=role-name,...; auths=auth-name,..."}' passwd.name > user_attr Copy the modified files to the /tmp directory on the LDAP server.# cp aliases auto_home_internal passwd shadow user_attr /tmp/name Add the entries in the files in Step 3 to the databases on the LDAP server.# /usr/sbin/ldapaddent -D "cn=directory manager" -w DM-password \ -a simple -f /tmp/name/aliases aliases # /usr/sbin/ldapaddent -D "cn=directory manager" -w DM-password \ -a simple -f /tmp/name/auto_home_internal auto_home_internal # /usr/sbin/ldapaddent -D "cn=directory manager" -w DM-password \ -a simple -f /tmp/name/passwd passwd # /usr/sbin/ldapaddent -D "cn=directory manager" -w DM-password \ -a simple -f /tmp/name/shadow shadow # /usr/sbin/ldapaddent -D "cn=directory manager" -w DM-password \ -a simple -f /tmp/name/user_attr user_attr In the following example, the administrator adds a new user to the trusted network. The user's information is stored originally in an NIS database. To protect the LDAP server password, the administrator runs the ldapaddent commands on the server.In Trusted Extensions, the new user can allocate devices and assume the Operator role. Because the user can assume a role, the user account does not get locked out. The user's minimum label is PUBLIC. The label at which the user works is INTERNAL, so jan is added to the auto_home_internal database. The auto_home_internal database automounts jan's home directory with read-write permissions .On the LDAP server, the administrator extracts user information from NIS databases.# ypcat -k aliases | grep jan.doe > aliases.jan # ypcat passwd | grep "Jan Doe" > passwd.jan # ypcat -k auto_home | grep jan.doe > auto_home_internal Then, the administrator reformats the entries for LDAP.# sed 's/ /:/g' aliases.jan > aliases # nawk -F: '{print $1":x:"$3":"$4":"$5":"$6":"$7}' passwd.jan > passwd # nawk -F: '{print $1":"$2":6445::::::"}' passwd.jan > shadow Then, the administrator creates a user_attr entry for Trusted Extensions.# nawk -F: '{print $1"::::lock_after_retries=no;profiles=Media User; labelview=internal,showsl;min_label=0x0002-08-08; clearance=0x0004-08-78;type=normal;roles=oper; auths=solaris.device.allocate"}' passwd.jan > user_attr Then, the administrator copies the files to the /tmp/jan directory.# cp aliases auto_home_internal passwd shadow user_attr /tmp/jan Finally, the administrator populates the server with the files in the /tmp/jan directory.# /usr/sbin/ldapaddent -D "cn=directory manager" -w a2b3c4d5e6 \ -a simple -f /tmp/jan/aliases aliases # /usr/sbin/ldapaddent -D "cn=directory manager" -w a2b3c4d5e6 \ -a simple -f /tmp/jan/auto_home_internal auto_home_internal # /usr/sbin/ldapaddent -D "cn=directory manager" -w a2b3c4d5e6 \ -a simple -f /tmp/jan/passwd passwd # /usr/sbin/ldapaddent -D "cn=directory manager" -w a2b3c4d5e6 \ -a simple -f /tmp/jan/shadow shadow # /usr/sbin/ldapaddent -D "cn=directory manager" -w a2b3c4d5e6 \ -a simple -f /tmp/jan/user_attr user_attr In Trusted Extensions, the labeled zones communicate with the X server through the global zone. Therefore, the labeled zones must have usable routes to the global zone. Also, options that were selected during a Solaris installation can prevent Trusted Extensions from using interfaces to the global zone.Description:Instead of running the netservices limited command before you added the Trusted Extensions packages, you ran the command in the global zone after you added the packages. Therefore, your labeled zones are unable to connect to the X server in the global zone. Solution:Run the following commands to open the services that Trusted Extensions requires to communicate between zones:# svccfg -s x11-server setprop options/tcp_listen = true # svcadm enable svc:/network/rpc/rstat:default Description:When you attempt to open a console window in a labeled zone, the following error appears in a dialog box:Action:DttermConsole,*,*,*,0 [Error] Action not authorized. Solution:Verify that the following two lines are present in each of the zone entries in the /etc/security/exec_attr file:All Actions:solaris:act:::*;*;*;*;*: All:solaris:act:::*;*;*;*;*:If these lines are not present, the Trusted Extensions package that adds these entries was not installed in the labeled zones. In this case, re-create the labeled zones. For the procedure, see Creating Labeled Zones. Description:If a labeled zone cannot successfully access the X server, you might see messages such as the following:Action failed. Reconnect to Solaris Zone? No route available Cannot reach globalzone-hostname:0 Cause:The labeled zones might not be able to access the X server for any of the following reasons:The zone is not initialized and is waiting for the sysidcfg process to complete. The labeled zone's host name is not recognized by the naming service that runs in the global zone. No interface is specified as all-zones. The labeled zone's network interface is down. LDAP name lookups fail. NFS mounts do not work. Steps toward a solution:Do the following:Log in to the zone.You can use the zlogin command or the Zone Terminal Console action.# zlogin -z zone-nameIf you cannot log in as superuser, use the zlogin -S command to bypass authentication. Verify that the zone is running.# zoneadm listIf a zone has a status of running, the zone is running at least one process. Address any problems that prevent the labeled zones from accessing the X server.Initialize the zone by completing the sysidcfg process.Run the sysidcfg program interactively. Answer the prompts in the Zone Terminal Console, or in the terminal window where you ran the zlogin command.To run the sysidcfg process noninteractively, you can do one of the following:Specify the Initialize item for the /usr/sbin/txzonemgr script.The Initialize item enables you to supply default values to the sysidcfg questions. Write your own sysidcfg script.For more information, see the sysidcfg4 man page. Verify that the X server is available to the zone.Log in to the labeled zone. Set the DISPLAY variable to point to the X server, and open a window.# DISPLAY=global-zone-hostname:n.n # export DISPLAY # /usr/openwin/bin/xclockIf a labeled window does not appear, the zone networking has not been configured correctly for that labeled zone. Configure the zone's host name with the naming service.The zone's local /etc/hosts file is not used. Instead, equivalent information must be specified in the global zone or on the LDAP server. The information must include the IP address of the host name that is assigned to the zone. No interface is specified as all-zones.Unless all your zones have IP addresses on the same subnet as the global zone, you might need to configure an all-zones (shared) interface. This configuration enables a labeled zone to connect to the X server of the global zone. If you want to restrict remote connections to the X server of the global zone, you can use vni0 as the all-zones address.If you do not want an all-zones interface configured, you must provide a route to the global zone X server for each zone. These routes must be configured in the global zone. The labeled zone's network interface is down.# ifconfig -aUse the ifconfig command to verify that the labeled zone's network interface is both UP and RUNNING. LDAP name lookups fail.Use the ldaplist command to verify that each zone can communicate with the LDAP server or the LDAP proxy server. On the LDAP server, verify that the zone is listed in the tnrhdb database. NFS mounts do not work.As superuser, restart automount in the zone. Or, add a crontab entry to run the automount command every five minutes. The following two tasks enable you to transfer exact copies of configuration files to every Trusted Extensions system at your site. The final task enables you to remove Trusted Extensions customizations from a Solaris system.When copying to portable media, label the media with the sensitivity label of the information.During installation, superuser or an equivalent role copies administrative files to and from portable media. Label the media with Trusted Path. To copy administrative files, you must be superuser or in a role in the global zone. Allocate the appropriate device.Use the Device Allocation Manager, and insert clean media.  For details, see How to Allocate a Device in Trusted Extensions in Solaris Trusted Extensions User’s Guide. In Solaris Trusted Extensions (CDE), a File Manager displays the contents of the portable media. In Solaris Trusted Extensions (JDS), a File Browser displays the contents. In In this procedure, File Manager is used to refer to this GUI. Open a second File Manager. Navigate to the folder that contains the files to be copiedFor example, you might have copied files to an /export/clientfiles folder. For each file, do the following:Highlight the icon for the file. Drag the file to the File Manager for the portable media. Deallocate the device.For details, see How to Deallocate a Device in Trusted Extensions in Solaris Trusted Extensions User’s Guide. On the File Manager for the portable media, choose Eject from the File menu.Remember to physically affix a label to the media with the sensitivity label of the copied files. The system administrator wants to ensure that every machine is configured with the same settings. So, on the first machine that is configured, she creates a directory that cannot be deleted between reboots. In that directory, the administrator places the files that should be identical or very similar on all systems.For example, she copies the Trusted Extensions toolbox that the Solaris Management Console uses for the LDAP scope, /var/sadm/smc/toolboxes/tsol_ldap/tsol_ldap.tbx. She has customized remote host templates in the tnrhtp file, has a list of DNS servers, and audit configuration files. She also modified the policy.conf file for her site. So, she copies the files to the permanent directory.# mkdir /export/commonfiles # cp /etc/security/policy.conf \ /etc/security/audit_control \ /etc/security/audit_startup \ /etc/security/tsol/tnrhtp \ /etc/resolv.conf \ /etc/nsswitch.conf \ /export/commonfilesShe uses the Device Allocation Manager to allocate a diskette in the global zone, and transfers the files to the diskette. On a separate diskette, labeled ADMIN_HIGH, she puts the label_encodings file for the site.When she copies the files onto a system, she modifies the dir: entries in the /etc/security/audit_control file for that system. It is safe practice to rename the original Trusted Extensions file before replacing the file. When configuring a system, the root role renames and copies administrative files. To copy administrative files, you must be superuser or in a role in the global zone. Allocate the appropriate device.For details, see How to Allocate a Device in Trusted Extensions in Solaris Trusted Extensions User’s Guide.In Solaris Trusted Extensions (CDE), a File Manager displays the contents of the portable media. In Solaris Trusted Extensions (JDS), a File Browser displays the contents. In this procedure, File Manager is used to refer to this GUI. Insert the media that contains the administrative files. If the system has a file of the same name, copy the original file to a new name.For example, add .orig to the end of the original file:# cp /etc/security/tsol/tnrhtp /etc/security/tsol/tnrhtp.orig Open a File Manager. Navigate to the desired destination directory, such as /etc/security/tsol For each file that you want to copy, do the following:In the File Manager for the mounted media, highlight the icon for the file. Then, drag the file to the destination directory in the second File Manager. Deallocate the device.For details, see How to Deallocate a Device in Trusted Extensions in Solaris Trusted Extensions User’s Guide. When prompted, eject and remove the media. In this example, roles are not yet configured on the system. The root user needs to copy configuration files to portable media. The contents of the media will then be copied to other systems. These files are to be copied to each system that is configured with Trusted Extensions software.The root user allocates the floppy_0 device in the Device Allocation Manager and responds yes to the mount query. Then, the root user inserts the diskette with the configuration files and copies them to the disk. The diskette is labeled Trusted Path.To read from the media, the root user allocates the device on the receiving host, then downloads the contents.If the configuration files are on a tape, the root user allocates the mag_0 device. If the configuration files are on a CD-ROM, the root user allocates the cdrom_0 device. To remove Trusted Extensions from your Solaris system, you perform specific steps to remove Trusted Extensions customizations to the Solaris system. As in the Solaris OS, archive any data in the labeled zones that you want to keep. Remove the labeled zones from the system.For details, see How to Remove a Non-Global Zone in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones. Remove the Trusted Extensions packages from the system.If you added the Trusted Extensions packages by using the install wizard, use the uninstall wizard.The wizard can be found in the /var/sadm/tx directory.# cd /var/sadm/tx # java uninstall_Solaris_Trusted_ExtensionsYou can also use the prodreg command. For details, see prodreg1M command. If you added the Trusted Extensions packages by using the pkgadd command, use the pkgrm command.For details, see the pkgrm1M man page. Run the bsmunconv command.For the effect of this command, see the bsmunconv1M man page. Reboot the system. Configure the system.Various services might need to be configured for your Solaris system. Candidates include auditing, basic networking, naming services, and file system mounts.