Chapter 1 Trusted Solaris 8 2/04 Release Notes

Use Trusted Solaris Installation and Configuration (PN 816-1040-10) to configure the Trusted Solaris^TM Operating System. The differences between a Trusted Solaris Operating System and a Solaris^TM Operating System require planning and guidance during installation and configuration. Differences occur in labels, clearance confirmations, obligatory passwords, security configuration choices, name service domain setup, secure network setup, and no superuser.

The Trusted Solaris 8 2/04 release upgrades the Trusted Solaris 8 HW 7/03 release to use UltraSPARC® IV processors. The new release also enhances the following software with security:

• Solaris 8 2/04 release

• X Windows, version 11.0

• CDE 1.4.8 (Common Desktop Environment)

• Solaris Management Console 2.0.0 administrative interface

This release includes the following fixes:

• Bug fixes for Solaris software that affect Trusted Solaris software. See Table 1–1.

• Patches that were released to patch earlier Trusted Solaris releases, and bug fixes. See Table 1–2.

• All Solaris patches that were included in the Solaris 8 2/04 release. Use the showrev -p command to list the patches that have been applied to the system.

You can safely apply some patches that are available for the standard releases of Solaris software, CDE, X Windows, or the Solaris Management Console. Trusted Solaris software is packaged to reflect differences from Solaris software packages only where such differences exist.

The sections in this document are as follows:

• Getting Help

• Supported Hardware

• Future Trusted Solaris Releases

• Solaris Bug Fixes Incorporated Into the Trusted Solaris 8 2/04 Release

• Trusted Solaris Bugs Fixed in the Trusted Solaris 8 2/04 Release

• Man Page Changes or Additions in the Trusted Solaris 8 2/04 Release

• Known Problems With the Software

Getting Help

The docs.sun.com^SM web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. The URL is http://docs.sun.com.

For additional information about the Trusted Solaris product, visit the http://www.sun.com/trustedsolaris web site.

For help from the user community in a public forum, visit the http://www.sun.com/supporttraining web site. Select Forums. After selecting Trusted Solaris Security, you can click the Register button to register for and participate in the Trusted Solaris Support Forum.

Reading About the Changes and Features in This Release

The following books contain information about this release:

Trusted Solaris 8 2/04 Release Notes

For bugs that have been fixed between the Trusted Solaris 8 HW 12/02 and Trusted Solaris 8 HW 7/03 releases, and for changes from the Trusted Solaris 8 HW 7/03 release to this release. Also contains a list of interfaces that might be changed in future releases.

Solaris 8 2/04 What’s New Supplement

For features that the Trusted Solaris 8 2/04 release inherits from the Solaris 8 2/04 release. Features can include hardware information.

Solaris 8 (SPARC Platform Edition) 2/04 Release Notes

For late-breaking news about the Solaris 8 2/04 release and hardware information.

Solaris 8 2/04 Sun Hardware Platform Guide

For features that have been added since the Solaris 8 HW 7/03 release.

Solaris 8 2/04 Release Notes Supplement

See the Solaris 8 2/04 Update Collection, http://docs.sun.com/db/coll/834.4.

Supported Hardware

The Trusted Solaris 8 2/04 release supports the workstation, server, and peripherals hardware that are supported by the Solaris 8 2/04 release. The Trusted Solaris 8 HW 7/03 and Trusted Solaris 8 2/04 releases also support the Sun Fire^TM V60x and Sun Fire V65x hardware platforms.

For the hardware that is supported by the Solaris 8 2/04 release, see Reading About the Changes and Features in This Release.

For the Sun Fire V60x and Sun Fire V65x servers, do the following steps to reach documentation that can be downloaded:

1. Go to the Sun hardware documentation web site, http://www.sun.com/products-n-solutions/hardware/docs.

2. In the left-hand column, click Servers.

3. Click Sun Fire V60x and V65x to reach the list of documentation.

Future Trusted Solaris Releases

Information in this section is provided to help assist customers and vendors with early planning for migration to future releases. This information is based on information that is presently available.

In the future, Sun might no longer supply Trusted Solaris software as a product that is based on modifying the Solaris kernel. Instead, Sun might produce the functionality as software that is designed to meet or exceed the requirements of the Common Criteria's Labeled Security Protection Profile. Sun might also include features such as the multilevel secure desktop and trusted networking. This functionality might be installed with a future release of the Solaris operating system.

Some features that might change are:

• The name of the product might change.

• The information labels (ILs) feature was removed in the Trusted Solaris 7 release, but programmatic storage for ILs was maintained in order to preserve compatibility. That storage might be removed in a future release.

• Support for the TSIX protocol might be dropped.

• The NIS+ naming service might be replaced by another naming service in future releases.

• The formats of configuration files might change. The file formats are described in section 4 of the Reference Manual of earlier releases. For example, the entries and the fields in the exec_attr file and the user_attr file might change.

• The names of privileges might change. Therefore, interfaces that check for specific privileges might change correspondingly. For example, the privilege macros that are described on the priv_macros(5) man page might change.

Your experience when using future releases of Trusted Solaris software will generally be the same as your current experience. However, the underlying implementation for features such as privileges, file system attributes, and networking might change. For example, the interfaces that are documented in the Trusted Solaris Reference Manual might change.

For information about specific interfaces that might change in a future Trusted Solaris release, see Appendix A, Possible Interface Changes in a Future Trusted Solaris Release.

Solaris Bug Fixes Incorporated Into the Trusted Solaris 8 2/04 Release

The Trusted Solaris 8 2/04 release includes all product patches and bug fixes that were incorporated into the Solaris 8 2/04 release. This release also includes some of the patches for the Solaris 8 2/04 release. To see the list of patches, use the showrev -p command.

Additional bug fixes that are included in the Trusted Solaris 8 2/04 release are listed in the following table. Some bug fixes are for software that is part of the Trusted Solaris release, such as CDE or the Solaris Management Console.

Trusted Solaris Bugs Fixed in the Trusted Solaris 8 2/04 Release

The following table describes bugs from earlier Trusted Solaris releases that are fixed in this release. This section includes a description of how to use a new feature on the CDE menu.

To Customize Workspace Menu

The fix for bug 4956889 adds a new feature to the Workspace Menu. The feature enables a user to add applications to the Workspace Menu.

Procedure: Follow these steps to customize and update the workspace menu.

1. Choose the applications that you want by clicking the Customize Menu ... item in the Workspace Menu.

   A File Manager appears with the selections that are available at that label for the Workspace Menu.

2. Make your choices for this workspace at this label.

3. Confirm your choices by clicking the File menu > Update Workspace Menu.

4. Restart the window manager by clicking Windows > Restart Workspace Menu from the Workspace Menu.

   After the window manager restarts, the new selection displays in the Workspace Menu.

Man Page Changes or Additions in the Trusted Solaris 8 2/04 Release

All Trusted Solaris man pages, including any new or updated man pages, are available in Trusted Solaris 8 2/04 software by using the man command.

Known Problems With the Software

This section identifies known problems in the Trusted Solaris 8 2/04 software, describes the problems, and suggests solutions. These bugs might or might not be fixed in a future release.

Communication is Broken Between tsol and tsol_cipso Labels (6251082)

On both SPARC® and x86 platforms, communication is broken between hosts with tsol and tsol_cipso labels. The ping and rup commands work between the hosts. The commands telnet, rsh, and ftp do not work for local users within the range CONFIDENTIAL to TOP_SECRET. The commands telnet, rsh, and ftp work for ADMIN_LOW, UNCLASSIFIED and ADMIN_HIGH labels. The problem is consistent on V490, V890, SB1000, and V440R platforms, but is not observed on SB1500 and some x86 servers.

Workaround: None.

Trusted Solaris dtwm Patch Causes Function Key Problems (6282792)

When patch 16336-07 or patch 119038-01 is installed, the Front and Open keys on the Sun keyboard fail to work once a role has been assumed.

Workaround: Do not use the Front or Open key.

On a Trusted Solaris 8 HW 12/02 system, do not install patch 116336-07. On a Trusted Solaris 8 HW 7/03 system, do not install patch 119038-01.

x86: Installation Difference Between the Trusted Solaris 8 4/01 Release and the Trusted Solaris 8 2/04 Release

Trusted Solaris Installation and Configuration instructs the customer to remove the boot diskette.

Workaround: When the installation program informs you to remove the boot diskette, do so. The CD-ROM is still inserted. During the BIOS/system self-tests, you can remove the CD.

If you have installed the software from a CD-ROM, leave the CD-ROM in the drive. If you are doing an upgrade install, the system does not automatically reboot after the installation of the first CD.

• On most systems, if you fail to remove the CD during the self-tests, the device configuration screen appears. You can then navigate the menus in the Device Configuration Assistant (DCA) and select the hard drive to boot from. You then remove the CD when the installation program prompts you to do so.

• If you are installing a Sun Fire V60x or a Sun Fire V65x system, you must remove the CD during the BIOS/system self-tests. You are not prompted to remove the CD. You then boot directly from the disk.

Client Cannot Contact Trusted Solaris Net Install Server (4907769)

A network install server that is running the Trusted Solaris operating system is unable to communicate with Trusted Solaris clients that the install server has installed until the server is rebooted.

Workaround: If the client will need to be in contact with the network install server, reboot the server. If there are multiple clients to install, reboot the server after the client installations are complete.

Alternatively, you can install Trusted Solaris clients from a network install server that is running the Solaris operating system.

Problem With Solaris Management Console and Java 1.2.2_17a (4958563)

A black line appears at the bottom of a small number of Solaris Management Console dialog boxes. The line obscures some buttons.

Workaround:

• Resize the dialog box to see the buttons.

• Install the Java fix (version 1.2.2_17b or higher) for this bug when the fix is available.

ftp Through CIPSO Router Does Not Work (4797140)

When an unlabeled machine sends a full packet, an intervening labeled gateway adds the CIPSO header. The addition of the CIPSO header makes the packet larger than 1500 bytes, and therefore the packet is dropped due to size.

Workaround: By setting the MTU on the system to be smaller, the problem is solved. Then, when the CIPSO label is added, the packet is still a legal size.

xterm Windows Terminate When Cutting and Pasting With xinerama (4895240)

Cutting and pasting between xterm windows when using xinerama causes the following problems:

• The xterm application that the data is copied from terminates. Termination happens at the instant that the data is pasted.

• Running the mozilla application results in a BadWindow error, with mozilla failing to run.

• The title bar and label bar of exposed windows is not properly redrawn.

Workaround: None.

Languages CD Is Not Supported

This release supports only the C locale (U.S. English). Thus, no Languages CD is provided.

Communication Between TSIX Host Types With IPsec AH Is Broken (4471447)

Network packets that use the TSIX protocol are not processed correctly when AH headers are present.

Workaround: None.

IKE Does Not Work With the TSOL Host Type (4548783)

Network packets that are labeled with the TSOL protocol are not processed correctly by IKE in the SunScreen^TM 3.2 product. The SunScreen product is co-packaged with this release. The SunScreen log messages show IKE_INVALID_COOKIE.

The SunScreen software properly processes TSOL-labeled network traffic that is in clear text. The SunScreen IKE software also behaves correctly in the Trusted Solaris operating environment to protect traffic between unlabeled network connections.

Workaround: None.

nisaddent Causes a SIGSEGV Error When Adding to tnrhdb (4491941)

A SIGSEGV error is produced when using the nisaddent -avf command to add an incorrectly formatted file to the tnrhdb NIS+ map. The incorrectly formatted file produces a core dump.

Workaround: The nisaddent command works correctly with a valid input file. To ensure that the input file has fields separated by colons and not by spaces, use niscat -s : when dumping an NIS+ table that will be used later as input to NIS+.

File System Label Ranges Are Not Enforced for Unlabeled NFS File Systems (4150441)

This bug occurs in a very unusual situation. The administrator must have consciously configured an NFS remote host to be at one label, and the label range to be another label.

Workaround: To prevent the creation of files at the default label for the server, mount the file system as “read-only”. Existing files are unaffected, but the read-only mount option prevents the creation of files at a label outside the label range.

Graphical Window Manager Controls Do Not Work (4462771)

The new utilities sdtgwm, sdtwsm, and sdtwinlst and their corresponding actions in the Desktop_Apps folder generate errors, such as Warning: Query Module Not Running.

Workaround: None. These tools are inappropriate for users in the Trusted Solaris environment. Thus, the tools are not supported.

niscat Command Hangs and Spawns Multiple nisd Processes on an NIS+ Server (4430740)

The bug is known to occur when the Solaris Management Console is running on an NIS+ client or master and has loaded its toolbox from an NIS+ replica. Next, the replica is shut down and the Solaris Management Console is used to update any NIS+ maps. Since the machine from which the Solaris Management Console loaded its toolbox is down, the Solaris Management Console client has no way to communicate with the Solaris Management Console server, which is the machine from which the toolbox has been loaded.

Workaround: Do not use the Solaris Management Console to update NIS+ databases when an NIS+ replica is down. Use the standard NIS+ command-line interface instead.

Trusted Solaris Label Encodings File Requires Coding for ILs (4329208)

Although Trusted Solaris 8 software does not support information labels (ILs), the chk_encodings command fails with the following error if the label_encodings file omits information about ILs.

# chk_encodings label_encodings
   Label encodings conversion error at line 37:
      Can't find INFORMATION LABELS specification.
      Found instead: "SENSITIVITY LABELS:".
   label_encodings: label encodings syntax check failed.

Workaround: Copy a valid SENSITIVITY LABELS: section in your label_encodings file, and rename the section to INFORMATION LABELS:, as in:

INFORMATION LABELS: 
...
WORDS: 
...
REQUIRED COMBINATIONS: 
...
COMBINATION CONSTRAINTS:
...

See the label_encodings(4) man page for more information.

smosservice Command Fails to Create OS Server (4378498)

The Solaris Management Console commands smosservice and smdiskless do not work correctly.

Workaround: Set up diskless service manually. On the OS server, name and allocate the client disk partitions during the installation process.

Drag-and-Drop Operations Do Not Work for OPEN LOOK Applications (4095021)

Drag-and-drop operations do not work reliably for OPEN LOOK applications.

Workaround: Use the copy and paste keys with OPEN LOOK applications.

Nonexistent Location ID: FileManagerLabelsHelp (4477399)

This bug is seen when you perform the following steps:

1. Insert diskette.

   floppy_0 is allocated by Device Allocation Manager.

2. From File Manager, click the File menu and select Removable Media Manager.

3. Select the diskette icon. Click mouse button 3 to open the Labels menu item.

4. In Removable Media Manager - File Labels (the Trusted Solaris Label Builder), click the Help button at bottom right of the dialog box.

Workaround: Perform the following steps:

1. Click mouse button 3 on the Front Panel and select Help from the menu. The Workspace Manager – Help window appears.

2. In the Workspace Manager – Help window, scroll down in the top pane to Trusted Solaris Applications and select that text.

3. In the bottom pane, click Create Labels.

Solaris Management Console Mounts and Shares Tools Do Not Set or Modify Trusted Solaris Attributes (4496897)

The Solaris Management Console Mounts tool and Solaris Management Console Shares tool do not manipulate Trusted Solaris attributes.

Workaround: Use the Set Mount Points action and the Share Filesystems action to handle Trusted Solaris attributes. You can also use the Admin Editor on the /etc/vfstab file and the /etc/dfs/dfstab file.