OpenSolaris

Heads-up: Trusted Extensions changes

Date: Fri, 27 Jul 2007 16:54:13 -0700 (PDT)
From: Ric Aleshire <Ric.Aleshire at sun dot com>
To: on-all at eng dot sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Heads-up: Trusted Extensions changes

If you do not use Trusted Extensions, you can ignore this mail.

My putback of:

PSARC 2007/254 - Enabling method for Trusted Extensions
6533113 split install and enabling of Trusted Extensions
6533118 move TX source from TLC to ON gate
(etc...)

changes the install procedure for Trusted Extensions (TX).

Background:
~-----------
The initial delivery of Trusted Extensions to NV and S10U3 included
several add-on packages in the Extra Value directory, installed
separately from Solaris.  Installation of these packages automatically
enabled TX.

Changes:
~--------
With the above putback, the first of the add-on TX packages are
migrated into the WOS as of SNV71, and installed during Solaris
install.  As part of this, an enable/disable mechanism is added:
after installation (including separate install for remaining add-on
packages), TX is enabled by:

	svcadm enable labeld

Following this, TX can be configured as before.  (TX users who pick
this code up via bfu should also enable this service before rebooting,
to keep TX enabled.)

The Install Guide will soon be updated to reflect these changes; in the
meantime, internal users may refer to http://rampart.sfbay for current
instructions and general product info.  Note that the migration of the
remaining TX packages (for desktop, SMC, etc.) is in progress.

Please send questions and other correspondence to rampart-dev-team at sun dot com.

-Ric