Administering Trusted Extensions Remotely (Task Map)

The following task map describes the tasks used to administer a remote Trusted Extensions system.

How to Log In Remotely From the Command Line in Trusted Extensions

Before You Begin

The user and the role must be identically defined on the local and the remote system.

The role must have the Remote Login authorization. By default, this authorization is in the Remote Administration, and the Maintenance and Repair rights profiles.

The security administrator has completed the procedure Enable Remote Login by a Role in Trusted Extensions on every system that can be remotely administered. If the system can be administered from an unlabeled system, the procedure Enable Remote Login From an Unlabeled System has also been completed.

• From the workspace of a user who can assume a role, log in to the remote host.

  Use the rlogin command, the ssh command, or the ftp command.

  • If the rlogin -l or ssh command is used to log in, all commands that are in the role's rights profiles are available.

  • If the ftp command is used, see the ftp(1) man page for the commands that are available.

How to Enable Specific Users to Log In Remotely to the Global Zone in Trusted Extensions

The user's default label range and the zone's default behavior are changed to enable remote login by a non-role. You might want to complete this procedure for a tester who is using a remote labeled system. For security reasons, the tester's system should be running a disjoint label from other users.

Before You Begin

You must have a very good reason why this user can log in to the global zone.

You must be in the Security Administrator role in the global zone.

1. To enable specific users to log in to the global zone, assign them an administrative label range.

   Assign a clearance of ADMIN_HIGH and a minimum label of ADMIN_LOW to each user. For details, see How to Modify a User's Label Range.

   The user's labeled zones must also permit login.

2. To enable remote login from a labeled zone into the global zone, do the following.
   1. Add a multilevel port for remote login to the global zone.

      Port 513 over the TCP protocol enables remote login. For an example, see How to Create a Multilevel Port for a Zone.

   2. Read the tnzonecfg changes into the kernel.

      # tnctl -fz /etc/security/tsol/tnzonecfg

   3. Restart the remote login service.

      # svcadm restart svc:/network/login:rlogin

How to Use Xvnc to Remotely Access a Trusted Extensions System

Virtual Network Computing (vnc) technology connects a client to a remote server, then displays the desktop of the remote server in a window on the client. Xvnc is the UNIX version of vnc, which is based on a standard X server. In Trusted Extensions, a client on any platform can connect to an Xvnc that is running Trusted Extensions software, log in to the Xvnc server, then display and work on a multilevel desktop.

Before You Begin

You have installed and configured Trusted Extensions software on the system that is going to be used as the Xvnc server. You have created and booted the labeled zones. Your Xvnc server recognizes the vnc clients by hostname or IP address.

You are superuser in the global zone of the system that is going to be used as the Xvnc server.

1. Configure the Xvnc server.

   For more information, see the Xvnc(1) and vncconfig(1) man pages.

   1. Use the console-kit-daemon to configure the X server.

      Oracle Solaris uses GNOME Display Manager (GDM) version 2.8. In this GDM version, Xvnc is configured by using the ConsoleKit interfaces. These interfaces manage the switching of sessions and session migration for mechanisms such as virtual terminals. To modify the interfaces for Xvnc, see section "ConsoleKit Display Configuration" in the console-kit-daemon(1M) man page.

   2. Make Xvnc available to all zones.

      Follow option 3 in the the following blog entry : Configuring xvnc for Trusted Extensions.

      Because Trusted Extensions requires all zones to connect to the Xvnc server in the global zone, you must do one of the following:

      • Make Xvnc available by using UNIX domain sockets.

        This method is preferable because it does not require a privileged port.

      • Make Xvnc privileged to bind to a multilevel port (MLP) that uses the TCP protocol.

        Because the ports 6000 through 6003 are already configured as MLPs, Xvnc must be a privileged process. You must assign the net_bindmlp to the Xvnc process. Without this privilege, the DISPLAY variable is unix:4, which indicates that the bind is single-level. Non-global zones cannot bind to a single-level port in the global zone.

2. Reboot the server or start the Xvnc server.

   # reboot

   After reboot, verify that the Xvnc program is running.

   # ps -ef | grep Xvnc
     root  2145  932  0  Apr 10  ?  6:15 /usr/X11/bin/Xvnc ...

3. On every vnc client of the Trusted Extensions Xvnc server, install vnc client software.

   For the client system, you have a choice of software. You can use Sun vnc software from the Oracle Solaris repository.

4. In a terminal window on a vnc client, connect to the server.

   % /usr/bin/vncviewer Xvnc-server-hostname

5. In the window that displays, type your name and password.

   Continue with the login procedure. For a description of the remaining steps, see Logging In to Trusted Extensions in Oracle Solaris Trusted Extensions User Guide.

   If you logged in to the server as superuser, you can administer the server immediately. If you logged in to the server as a user, you must assume a role to administer the system.