Managing Devices in Trusted Extensions (Task Map)

The following task map describes procedures to protect devices at your site.

How to Configure a Device in Trusted Extensions

By default, an allocatable device has a label range from ADMIN_LOW to ADMIN_HIGH and must be allocated for use. Also, users must be authorized to allocate the device. These defaults can be changed.

The following devices can be allocated for use:

• audion – Indicates a microphone and speaker

• cdromn – Indicates a CD-ROM drive

• floppyn – Indicates a diskette drive

• mag_tapen – Indicates a tape drive (streaming)

• rmdiskn – Indicates a removable disk, such as a JAZ or ZIP drive, or USB hot-pluggable media

Before You Begin

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

1. From the Trusted Path menu, select Allocate Device.

   The Device Manager appears.

   
   
2. View the default security settings.

   Click Administration, then highlight the device. The following figure shows an audio device that is being viewed by the root role.

   
   
3. (Optional) Restrict the label range on the device.
   1. Set the minimum label.

      Click the Min Label button. Choose a minimum label from the label builder. For information about the label builder, see Label Builder in Trusted Extensions.

   2. Set the maximum label.

      Click the Max Label... button. Choose a maximum label from the label builder.

4. Specify if the device can be allocated locally.

   In the Device Configuration dialog box, under For Allocations From Trusted Path, select an option from the Allocatable By list. By default, the Authorized Users option is checked. Therefore, the device is allocatable and users must be authorized.

   • To make the device nonallocatable, click No Users.

     When configuring a printer, frame buffer, or other device that must not be allocatable, select No Users.

   • To make the device allocatable, but to not require authorization, click All Users.
5. Specify if the device can be allocated remotely.

   In the For Allocations From Non-Trusted Path section, select an option from the Allocatable By list. By default, the Same As Trusted Path option is checked.

   • To require user authorization, select Allocatable by Authorized Users.
   • To make the device nonallocatable by remote users, select No Users.
   • To make the device allocatable by anyone, select All Users.
6. If the device is allocatable, and your site has created new device authorizations, select the appropriate authorization.

   The following dialog box shows the solaris.device.allocate authorization is required to allocate the cdrom0 device.

   
   

   To create and use site-specific device authorizations, see Customizing Device Authorizations in Trusted Extensions (Task Map).

7. To save your changes, click OK.

How to Revoke or Reclaim a Device in Trusted Extensions

If a device is not listed in the Device Manager, it might already be allocated or it might be in an allocate error state. The system administrator can recover the device for use.

Before You Begin

You must be in the System Administrator role in the global zone. This role includes the solaris.device.revoke authorization.

1. From the Trusted Path menu, select Allocate Device.

   In the following figure, the audio device is already allocated to a user.

   
   
2. Click the Administration button.
3. Check the status of a device.

   Select the device name and check the State field.

   • If the State field is Allocate Error State, click the Reclaim button.
   • If the State field is Allocated, do one of the following:
     • Ask the user in the Owner field to deallocate the device.
     • Force deallocation of the device by clicking the Revoke button.
4. Close the Device Manager.

How to Protect Nonallocatable Devices in Trusted Extensions

The No Users option in the Allocatable By section of the Device Configuration dialog box is used most often for the frame buffer and printer, which do not have to be allocated to be used.

Before You Begin

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

1. From the Trusted Path menu, select Allocate Device.
2. In the Device Manager, click the Administration button.
3. Select the new printer or frame buffer.
   1. To make the device nonallocatable, click No Users.
   2. (Optional) Restrict the label range on the device.
      1. Set the minimum label.

         Click the Min Label... button. Choose a minimum label from the label builder. For information about the label builder, see Label Builder in Trusted Extensions.

      2. Set the maximum label.

         Click the Max Label... button. Choose a maximum label from the label builder.

Example 21-1 Preventing Remote Allocation of the Audio Device

The No Users option in the Allocatable By section prevents remote users from hearing conversations around a remote system.

The security administrator configures the audio device in the Device Manager as follows:

Device Name: audio
For Allocations From: Trusted Path
Allocatable By: Authorized Users
Authorizations: solaris.device.allocate

Device Name: audio
For Allocations From: Non-Trusted Pathh
Allocatable By: No Users

How to Add a Device_Clean Script in Trusted Extensions

If no device_clean script is specified at the time a device is created, the default script, /bin/true, is used.

Before You Begin

Have ready a script that purges all usable data from the physical device and that returns 0 for success. For devices with removable media, the script attempts to eject the media if the user does not do so. The script puts the device into the allocate error state if the medium is not ejected. For details about the requirements, see the device_clean(5) man page.

You must be in the root role in the global zone.

1. Copy the script into the /etc/security/lib directory.
2. In the Device Properties dialog box, specify the full path to the script.
   1. Open the Device Manager.
   2. Click the Administration button.
   3. Select the name of the device, and click the Configure button.
   4. In the Clean Program field, type the full path to the script.
3. Save your changes.