Chapter 17 Managing Devices for Trusted Extensions (Tasks)

This chapter describes how to administer and use devices on a system that is configured with Solaris Trusted Extensions.

• Handling Devices in Trusted Extensions (Task Map)

• Using Devices in Trusted Extensions (Task Map)

• Managing Devices in Trusted Extensions (Task Map)

• Customizing Device Authorizations in Trusted Extensions (Task Map)

Handling Devices in Trusted Extensions (Task Map)

The following task map points to task maps for administrators and users for handling peripheral devices.

Using Devices in Trusted Extensions (Task Map)

In Trusted Extensions, all roles are authorized to allocate a device. Like users, roles must use the Device Allocation Manager. The Solaris allocate command does not work in Trusted Extensions. The following task map points to user procedures that include using devices to perform administrative tasks.

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.

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 Allocation Manager appears.

   

2. View the default security settings.

   Click Device Administration, then highlight the device. The following figure shows a CD-ROM drive with default security settings.

   

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 Allocation 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 Allocation 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 Device 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 Allocation 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 Allocation Manager, click the Device 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 17–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 Allocation 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 Configure a Serial Line for Logins

Before You Begin

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

1. Open the Solaris Management Console in the Files scope.

   Figure 17–1 Serial Ports Tool in the Solaris Management Console

   
   

2. Under Devices and Hardware, navigate to Serial Ports.

   Provide a password when prompted. Follow the online help to configure the serial port.

3. To change the default label range, open the Device Allocation Manager.

   The default label range is ADMIN_LOW to ADMIN_HIGH.

Example 17–2 Restricting the Label Range of a Serial Port

After creating a serial login device, the security administrator restricts the label range of the serial port to a single label, Public. The administrator sets the following values in the Device Administration dialog boxes.

Device Name: /dev/term/[a|b]
Device Type: tty
Clean Program: /bin/true
Device Map: /dev/term/[a|b]
Minimum Label: Public
Maximum Label: Public
Allocatable By: No Users

How to Configure an Audio Player Program for Use in Trusted CDE

The following procedure enables an audio player to open automatically in a Trusted CDE workspace when a user inserts a music CD. For the user's procedure, see the example in How to Allocate a Device in Trusted Extensions in Solaris Trusted Extensions User’s Guide.

In a Trusted JDS workspace, users specify the behavior of removable media just as they specify it in a non-trusted workspace.

Before You Begin

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

1. Edit the /etc/rmmount.conf file.

   Use the trusted editor. For details, see How to Edit Administrative Files in Trusted Extensions.

2. Add your site's CD player program to the cdrom action in the file.

   action media action_program.so path-to-program

Example 17–3 Configuring an Audio Player Program for Use

In the following example, the system administrator makes the workman program available to all users of a system. The workman program is an audio player program.

# /etc/rmmount.conf file
action cdrom action_workman.so /usr/local/bin/workman

How to Prevent the File Manager From Displaying After Device Allocation

By default, the File Manager displays when a device is mounted. If you are not mounting devices that have file systems, you might want to prevent the File Manager from displaying.

Before You Begin

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

1. Edit the /etc/rmmount.conf file.

   Use the trusted editor. For details, see How to Edit Administrative Files in Trusted Extensions.

2. Find the following filemgr actions:

   action cdrom action_filemgr.so action floppy action_filemgr.so

3. Comment out the appropriate action.

   The following example shows the action_filemgr.so actions commented out for both the cdrom and diskette devices.

   # action cdrom action_filemgr.so # action floppy action_filemgr.so

   When a CDROM or diskette is allocated, the File Manager does not display.

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 System Administrator role in the global zone.

1. Copy the script into the /etc/security/lib directory.

2. In the Device Administration dialog box, specify the full path to the script.

   1. Open the Device Allocation Manager.

   2. Click the Device 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.

Customizing Device Authorizations in Trusted Extensions (Task Map)

The following task map describes procedures to change device authorizations at your site.

How to Create New Device Authorizations

If no authorization is specified at the time a device is created, by default, all users can use the device. If an authorization is specified, then, by default, only authorized users can use the device.

To prevent all access to an allocatable device without using authorizations, see Example 17–1.

Before You Begin

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

1. Edit the auth_attr file.

   Use the trusted editor. For details, see How to Edit Administrative Files in Trusted Extensions.

2. Create a heading for the new authorizations.

   Use the reverse-order Internet domain name of your organization followed by optional additional arbitrary components, such as the name of your company. Separate components by dots. End heading names with a dot.

   domain-suffix.domain-prefix.optional.:::Company Header::help=Company.html

3. Add new authorization entries.

   Add the authorizations, one authorization per line. The lines are split for display purposes. The authorizations include grant authorizations that enable administrators to assign the new authorizations.

   domain-suffix.domain-prefix.grant:::Grant All Company Authorizations:: help=CompanyGrant.html domain-suffix.domain-prefix.grant.device:::Grant Company Device Authorizations:: help=CompanyGrantDevice.html domain-suffix.domain-prefix.device.allocate.tape:::Allocate Tape Device:: help=CompanyTapeAllocate.html domain-suffix.domain-prefix.device.allocate.floppy:::Allocate Floppy Device:: help=CompanyFloppyAllocate.html

4. Save the file and close the editor.

5. If you are using LDAP as your naming service, update the auth_attr entries on the Sun Java System Directory Server (LDAP server).

   For information, see the ldapaddent(1M) man page.

6. Add the new authorizations to the appropriate rights profiles. Then assign the profiles to users and roles.

   Use the Solaris Management Console. Assume the Security Administrator role, then follow the Solaris procedure How to Create or Change a Rights Profile in System Administration Guide: Security Services.

7. Use the authorization to restrict access to tape and diskette drives.

   Add the new authorizations to the list of required authorizations in the Device Allocation Manager. For the procedure, see How to Add Site-Specific Authorizations to a Device in Trusted Extensions.

Example 17–4 Creating Fine-Grained Device Authorizations

A security administrator for NewCo needs to construct fine-grained device authorizations for the company.

First, the administrator writes the following help files, and places the files in the /usr/lib/help/auths/locale/C directory:

Newco.html
NewcoGrant.html
NewcoGrantDevice.html
NewcoTapeAllocate.html
NewcoFloppyAllocate.html

Next, the administrator adds a header for all of the authorizations for newco.com in the auth_attr file.

# auth_attr file
com.newco.:::NewCo Header::help=Newco.html

Next, the administrator adds authorization entries to the file:

com.newco.grant:::Grant All NewCo Authorizations::
help=NewcoGrant.html
com.newco.grant.device:::Grant NewCo Device Authorizations::
help=NewcoGrantDevice.html
com.newco.device.allocate.tape:::Allocate Tape Device::
help=NewcoTapeAllocate.html
com.newco.device.allocate.floppy:::Allocate Floppy Device::
help=NewcoFloppyAllocate.html

The lines are split for display purposes.

The auth_attr entries create the following authorizations:

• An authorization to grant all NewCo's authorizations

• An authorization to grant NewCo's device authorizations

• An authorization to allocate a tape drive

• An authorization to allocate a diskette drive

Example 17–5 Creating Trusted Path and Non-Trusted Path Authorizations

By default, the Allocate Devices authorization enables allocation from the trusted path and from outside the trusted path.

In the following example, site security policy requires restricting remote CD-ROM allocation. The security administrator creates the com.someco.device.cdrom.local authorization. This authorization is for CD-ROM drives that are allocated with the trusted path. The com.someco.device.cdrom.remote authorization is for those few users who are allowed to allocate a CD-ROM drive outside the trusted path.

The security administrator creates the help files, adds the authorizations to the auth_attr database, adds the authorizations to the devices, and then places the authorizations in rights profiles. The profiles are assigned to users who are allowed to allocate devices.

• The following are the auth_attr database entries:

  com.someco.:::SomeCo Header::help=Someco.html com.someco.grant:::Grant All SomeCo Authorizations:: help=SomecoGrant.html com.someco.grant.device:::Grant SomeCo Device Authorizations:: help=SomecoGrantDevice.html com.someco.device.cdrom.local:::Allocate Local CD-ROM Device:: help=SomecoCDAllocateLocal.html com.someco.device.cdrom.remote:::Allocate Remote CD-ROM Device:: help=SomecoCDAllocateRemote.html

• The following is the Device Allocation Manager assignment:

  The Trusted Path enables authorized users to use the Device Allocation Manager when allocating the local CD-ROM drive.

  Device Name: cdrom_0 For Allocations From: Trusted Path Allocatable By: Authorized Users Authorizations: com.someco.device.cdrom.local

  The Non-Trusted Path enables users to allocate a device remotely by using the allocate command.

  Device Name: cdrom_0 For Allocations From: Non-Trusted Path Allocatable By: Authorized Users Authorizations: com.someco.device.cdrom.remote

• The following are the rights profile entries:

  # Local Allocator profile com.someco.device.cdrom.local # Remote Allocator profile com.someco.device.cdrom.remote

• The following are the rights profiles for authorized users:

  # List of profiles for regular authorized user Local Allocator Profile ... # List of profiles for role or authorized user Remote Allocator Profile ...

How to Add Site-Specific Authorizations to a Device in Trusted Extensions

Before You Begin

You must be in the Security Administrator role, or in a role that includes the Configure Device Attributes authorization. You must have already created site-specific authorizations, as described in How to Create New Device Authorizations.

1. Follow the How to Configure a Device in Trusted Extensions procedure.

   1. Select a device that needs to be protected with your new authorizations.

   2. Open the Device Administration dialog box.

   3. In the Device Configuration dialog box, click the Authorizations button.

      The new authorizations are displayed in the Not Required list.

   4. Add the new authorizations to the Required list of authorizations.

2. To save your changes, click OK.

How to Assign Device Authorizations

The Allocate Device authorization enables users to allocate a device. The Allocate Device authorization, and the Revoke or Reclaim Device authorization, are appropriate for administrative roles.

Before You Begin

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

If the existing profiles are not appropriate, the security administrator can create a new profile. For an example, see How to Create a Rights Profile for Convenient Authorizations.

1. Assign to the user a rights profile that contains the Allocate Device authorization.

   For assistance, see the online help. For the step-by-step procedure, see How to Change the RBAC Properties of a User in System Administration Guide: Security Services.

   The following profiles enable a role to allocate devices:

   • All Authorizations

   • Device Management

   • Media Backup

   • Media Restore

   • Object Label Management

   • Software Installation

   The following profiles enable a role to revoke or reclaim devices:

   • All Authorizations

   • Device Management

   The following profiles enable a role to create or configure devices:

   • All Authorizations

   • Device Security

Example 17–6 Assigning New Device Authorizations

In this example, the security administrator configures the new device authorizations for the system and assigns the rights profile with the new authorizations to trustworthy users. The security administrator does the following:

1. Creates new device authorizations, as in How to Create New Device Authorizations

2. In the Device Allocation Manager, adds the new device authorizations to the tape and diskette drives

3. Places the new authorizations in the rights profile, NewCo Allocation

4. Adds the NewCo Allocation rights profile to the profiles of users and roles who are authorized to allocate tape and diskette drives

Authorized users and roles can now use the tape drives and diskette drives on this system.