Installation and Configuration

The Trusted Solaris 2.5.1 system required the install team to configure labels during installation. In Trusted Solaris 7, the install team configures labels after installation.

Installation Differences

Installation on most hardware is identical to Solaris 7 installation. The two exceptions are:

• Solaris^TM Web Start is not supported

• Installing and configuring the Sun Enterprise^TM 10000 (E10000), also called Starfire^TM, is modified for Trusted Solaris security. See Trusted Solaris 7 Installation and Configuration on the Sun Enterprise 10000 for explanation and procedures.

Solaris installation features that Trusted Solaris 7 supports include:

• Trusted Solaris network and jumpstart installations are identical to Solaris network and jumpstart installations.

• sys-unconfig(1M) is supported.

• Unlike Trusted Solaris 2.5.1 installation, Trusted Solaris 7 installation does not offer label configuration options; sensitivity labels are configured after installation, not during. Therefore, the config_data file and its corresponding man page do not exist since there are no Trusted Solaris configuration options for network installations.

To distribute a site label encodings file during installation in Trusted Solaris 7 requires a customized JumpStart installation. See "Create a Finish Script to Add Files after Installation" in Trusted Solaris Installation and Configuration for an example.

Configuration Differences

To change default label configuration values, the security administrator edits the /etc/system file.

To enable the Stop-A shutdown mechanism, the security administrator edits the /etc/default/kbd file, except on the Sun Enterprise 10000, where the abort_enable keyword in the /etc/system file is still operative.

The Check Encodings System_Admin action enables an administrative role to install a site-specific label_encodings file.