We strongly recommend that you read and use Trusted Solaris Installation and Configuration (PN 805-8056-10) to guide you in configuring the Trusted Solaris operating environment. The differences between this secure operating environment and a base Solaris operating environment, such as -- clearance confirmations, obligatory passwords, security configuration choices, NIS+ domain setup, secure network setup, no superuser -- require planning and guidance during installation and configuration.
The Trusted Solaris 7 operating environment is an upgrade to the Trusted Solaris 2.5.1 release, and a security-enhanced version of the following software: Solaris 7 operating environment (including quarterly upgrades through 8/99), CDE 1.3 (Common Desktop Environment), and the SolsticeTM AdminSuiteTM 2.3 administrative interface. The release incorporates patches to the Trusted Solaris 2.5.1 operating environment, the window system (XW), and patches for the Solaris, CDE and Solstice AdminSuite releases.
Do not apply patches that may be available for the standard releases of Solaris software, CDE, or Solstice AdminSuite.
For assistance in using the document set, see the Trusted Solaris Roadmap (PN 805-8051-10) document.
The docs.sun.comSM 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.
Fatbrain.com, the Internet's most comprehensive professional bookstore, stocks select product documentation from Sun Microsystems, Inc.
For a list of documents and how to order them, visit the Sun Documentation Center on Fatbrain.com at http://www1.fatbrain.com/documentation/sun.
The docs.sun.comSM Web site enables you to access Sun technical documentation online. You can browse the http://docs.sun.com archive or search there for a specific book title or subject.
The Trusted Solaris 7 release supports the workstation, server, and peripherals hardware supported by the Solaris 7 release through the Solaris 8/99 update release. See Solaris 7 8/99 Sun Hardware Platform Guide in the Solaris 7 8/99 on Sun Hardware Collection.
The Trusted Solaris 7 release includes the following product patches and upgrades:
Table 1-1 Product Patches and Upgrades Integrated in Trusted Solaris 7
Product |
Patch No. |
Area Affected |
---|---|---|
CDE 1.3 |
106934-03 |
libDtSvc |
|
107001-01 |
Actions |
|
107011-01 |
sdtwebclient |
|
107022-03 |
Calendar Manager |
|
107072-01 |
Spell Checker |
|
107094-04 |
dtterm libDtTerm.so.2 |
|
107178-01 |
libDtHelp.so.1 |
|
107180-07 |
dtlogin |
|
107200-07 |
dtmail |
|
107219-02 |
dtprintinfo |
|
107226-05 |
dtwm |
|
107248-01 |
sdtaudio |
|
107306-01 |
dtfile |
|
107688-01 |
Actions |
|
107802-01 |
OBSOLETED by 107081 |
XWindows |
106725-01 |
mailtool vacation security |
|
106843-01 |
(JFP 7): OW workspace menu bug |
|
107078-12 |
Xsun |
|
107233-01 |
xterm |
|
107250-02 |
libsv8.so.1 |
|
107337-01 |
KCMS configure tool has a security vulnerability |
|
107374-01 |
Xview |
|
107546-02 |
Ultra 80 Support |
|
107723-01 |
printtool |
|
107807-01 |
xrdb |
|
107853-01 |
xdm patch |
Solstice AdminSuite 2.3 |
None |
No applicable patches. |
Solaris 7 |
various |
All patches incorporated into the Solaris 7 releases through the Solaris 8/99 update release. |
Trusted Solaris 2.5.1 |
|
Trusted Solaris 7 contains all the patches released for Trusted Solaris 2.5.1. |
ILs (Information Labels) have been removed from Trusted Solaris 7 software.
The Trusted Solaris 7 release supports Intel architecture and the Sun EnterpriseTM 10000.
The Trusted Solaris man pages are part of the SUNWman package.
See the Trusted Solaris 7 Transition Guide for the changes from Trusted Solaris 2.5.1 release to the current release.
The following bugs reported in the Trusted Solaris 2.5.1 Release Notes have been fixed in the Trusted Solaris 7 software:
Trusted Solaris Audit Administration contains the correct procedures for enabling and disabling auditing.
The network transports supplemental groups and audit information.
Installing Solaris 7 or an earlier version on a machine previously installed with the Trusted Solaris operating environment, no longer results in panics.
There are no duplicate entries when viewing authorization description database with the command man auth_desc.
Audit records for successful ftp identification and authentication are now generated.
Audit records are now generated for:
A user who does not have remote login authorization trying to log in.
A user trying to log in at an SL higher than the user's clearance.
A user trying to log in at an SL lower than the user's minimum label.
A role user trying to log in.
A user trying to log in to an expired account.
auditd(1M) does not drop or appear to drop audit records.
The audit(1M) command in the Audit Control execution profile is usable by the secadmin role.
128 authorizations are allowed, and the reserved authorizations are not parsed as if they are real authorizations.
The command rm -rf directory no longer panics the workstation.
This section identifies known problems in the Trusted Solaris 7 software, describes them, and suggests solutions to them. These bugs may or may not be fixed in a future release.
When you install a system and allocate space for diskless clients, it does not create directories named /export/root or /export/Trusted_Solaris_7. It also does not create any file listing the OS services.
Workaround: Name the partitions and allocate the space by customizing disk partitions during the installation program.
All executables under Tools/Boot need privileges before net install. Without the proper privileges on the executables, net install will fail.
Workaround: Run net install commands with all privileges.
In the root role, at label admin_low
,
use the Device Allocation Manager to allocate the CDROM drive, but do not
mount it.
Do not try to use the Volume Manager; it is disabled in the Trusted Solaris environment.
Click the triangle above the Style Manager on the Front Panel to display the Trusted Desktop subpanel. Click Device Allocation.
Double-click the CDROM device to move it to the Allocated Devices list.
Write down the device name for the CDROM drive as indicated in the "Insert disk into..." message in the Device Allocation window.
For example, if the message reads:
Insert disk into /dev/dsk/c0t2d0s0. Make sure disk is labeled ADMIN_LOW [ADMIN_LOW]. Press RETURN when cdrom_0 is ready, or ^C to cancel.then write down the device name, /dev/dsk/c0t2d0s0, before continuing.
Insert the Trusted Solaris Installation CD into the CDROM drive and press the Return key.
Answer n to the Do you want cdrom_0 mounted: (y/n)? n question.
In the root role, at label admin_low
,
make sure that /cdrom/cdrom0 exists.
If it does not, create it:
# mkdir -p /cdrom/cdrom0 |
Mount the CDROM with all allowed and forced privileges.
# mount -F hsfs -o ro -S "allowed=all;forced=all" cdrom_device
For example, for the CDROM on device /dev/dsk/c0t2d0s0, type:
# mount -F hsfs -o ro -S "allowed=all;forced=all" \ /dev/dsk/c0t2d0s0 /cdrom/cdrom0 |
Run the setup_install_server command, as described in the documentation.
Set up the .boot_attrs command to run with all privileges.
Assume the role secadmin.
Follow the procedure in "How to Update the Commands in a Role's Profile" in Trusted Solaris Installation and Configuration. Add the pathname of boot_attrs to the Custom Root Role profile, and give the command all privileges.
As root, run the .boot_attrs command with all privileges.
Assume the root role, and open a new terminal.
Check that the .boot_attrs command has all privileges.
See "To Verify That a Command is in a Role's Profile" in Trusted Solaris Installation and Configuration.
Change directory to OSdir/Trusted_Solaris_7/Tools/Boot.
# cd OSdir/Trusted_Solaris_7/Tools/Boot |
As root, run the .boot_attrs command.
# ../.boot_attrs |
Remove the command from the Custom Root Role profile when you are done.
The user cannot start any application, either from the front panel or from the workspace menu. This happened on some machines, and not on others.
Workaround: Restart the Workspace Manager.
Right-button on the background window and choose Window > Restart Workspace Manager.
Confirm.
Some /usr/man directories have permissions dr--r--r--.
Workaround: Add execute permission to the affected directories.
# chmod a+x /usr/man/sman1 /usr/man/sman3n /usr/man/sman3s /usr/man/sman3t /usr/man/sman3x /usr/man/sman39f |
There are cases where preselection in libbsm does not properly occur. The 64-bit t6 library calls t6peek_attr(3N) and t6last_attr(3N) fail in libbsm. auditwrite(3) does not work in 64-bit programs.
Workaround: Do not audit 64-bit programs.
Audit values for the msix (Trusted Solaris 2.5.1 and Trusted Solaris 7) host type in the tnrhtp do not correspond well with their Trusted Solaris 1.2 definitions.
Table 1-2 Audit Characteristics Defined in Different Trusted Solaris Releases
Trusted Solaris 7 Audit Characteristics |
Trusted Solaris 1.2 Audit Definitions in Trusted Solaris 7 tnrhtp |
---|---|
def_audit_uid = 4294967294 |
def_audit_auid=3 |
def_audit_mask = 0,0 |
def_audit_mask=0x0000000000000000 |
def_audit_terminal = 0,0 |
def_audit_termid=0x0000000000000000 |
|
def_audit_asid=0 |
Workaround: None.
Audit attributes prevent TCP from working properly between TSIX hosts.
Workaround: None.
The label_encodings file is not protected from reading.
Workaround: None.
The label_encodings(4) file contains locale-sensitive information. However, not all system programs that use the file are guaranteed to be locale-aware.
Workaround: In multi-byte locales or non-C locales where upper/lower case are not a direct mapping of the C locale, the classification and word names, short names, alternate names in the label_encodings file and all string labels in all databases must be in upper case only. Also, all labels must be entered in upper case only:
On the command line where the locale has not been set, or
To commands which do not call the library function setlocale(3C) with the correct locale.
The SUNWxcu4t package is not patched when the patch 106748-03 (SPARC)/106749-03 (Intel) is installed.
Workaround: In the root role, copy the patch files from the CD to the machine.
Mount the install CD.
Copy the original files on the machine to *.orig.
# cp -p /usr/xpg4/bin/make /usr/xpg4/bin/make.orig # cp -p /usr/xpg4/bin/get /usr/xpg4/bin/get.orig # cp -p /usr/xpg4/bin/sccs /usr/xpg4/bin/sccs.orig # cp -p /usr/xpg4/bin/delta /usr/xpg4/bin/delta.orig |
Copy all files in the usr/xpg4/bin/ directory from the CD to the machine.
# cp * /usr/xpg4/bin |
The following commands and library routines are not fully functional.
Requires privilege to contact a Trusted Solaris 1.2 workstation.
When used with the -v option to display an output file, dumps core if it encountered the TSIX SATMP protocol in the file.
Binary to string-coded and string-coded to binary label translation is not MT-safe.
libtsol() label functions change logging behavior of programs that use the label functions, that is, they change syslog parameters.
The mask argument of t6recvfrom() should contain the bits for the new attributes if t6new_attr(3N) is called. Instead, it contains the full set of attributes.
Should require sys_audit
privilege.
Currently network interfaces succeed in setting audit attributes without sys_audit
privilege. For TSOL connections, the
audit attributes are ignored. For TSIX connections, the audit attributes are
transmitted to the remote peer.
The swmtool(1M) utility does not work in the Trusted Solaris 7 operating environment.
Workaround: Use the pkgadd(1M) utility.
The bottom field, CIPSO Domain, is not shown in the window. The window cannot be resized to see the field.
Workaround: Make the font smaller.
Launch the Style Manager from the front panel.
Click on Font.
From the size list on the right of the window, select Small(3).
Click OK.
To get the new font, right-button on the background window, choose Window > Restart Workspace Manager. Confirm. Or, log out and log back in.
Read the files in SUNWrdm for information on the basic Solaris 7 environment.
Workaround: For late-breaking news, use this book, Trusted Solaris 7 Release Notes.
The version of the Trusted Solaris 7 Roadmap on the Trusted Solaris 7 Documentation CD contains inaccurate information in the section, "To Install the AnswerBook2 Server Software." The correct information is available in the printed version of the Trusted Solaris 7 Roadmap and in the README_en.txt file on the Trusted Solaris 7 Documentation CD.