Configuring Labeled Printing (Task Map)

The following task map describes common configuration procedures that are related to labeled printing.

How to Configure a Multilevel Print Server and Its Printers

Printers that are managed by a Trusted Extensions print server print labels on body pages, banner pages, and trailer pages. Such printers can print jobs within the label range of the print server. Any Trusted Extensions host that can reach the print server can use the printers that are connected to that server.

Before You Begin

Determine the print server for your Trusted Extensions network. You must be in the System Administrator role in the global zone on this print server.

1. Enable multilevel printing by configuring the global zone with the print server port, 515/tcp.
   1. Configure the zone and the MLP.

      Create a multilevel port (MLP) for the print server by adding the port to the global zone.

      ## tnzonecfg database
      global:ADMIN_LOW:1:111/tcp;111/udp;2049/tcp;6000-6003/tcp
      ;515/tcp:6000-6003/tcp;515/tcp

   2. Update the kernel.

      # tnctl -fz /etc/security/tsol/tnzonecfg

2. Define the characteristics of every connected printer.

   Use the command line. The Print Manager GUI does not work in the global zone.

   # lpadmin -p printer-name -v /dev/null \
   -o protocol=tcp -o dest=printer-IP-address:9100 -T PS -I postscript
   # accept printer-name
   # enable printer-name

3. Assign a printer model script to each printer that is connected to the print server.

   The model script activates the banner and trailer pages for the specified printer.

   For a description of the scripts, see Printer Model Scripts. If the driver name for the printer starts with Foomatic, then specify one of the foomatic model scripts. On one line, use the following command:

   $ lpadmin -p printer \
    -m { tsol_standard | tsol_netstandard | 
         tsol_standard_foomatic | tsol_netstandard_foomatic }

   If the default printer label range of ADMIN_LOW to ADMIN_HIGH is acceptable for every printer, then your label configuration is done.

4. In every labeled zone where printing is allowed, configure the printer.

   Use the all-zones IP address for the global zone as the print server.

   1. Log in as root to the zone console of the labeled zone.

      # zlogin -C labeled-zone

   2. Add the printer to the zone.

      # lpadmin -p printer-name -s all-zones-IP-address

   3. (Optional) Set the printer as the default.

      # lpadmin -d printer-name

5. In every labeled zone, test the printer.

   As root and as a regular user, perform the following steps:

   1. Print plain files from the command line.
   2. Print files from your applications, such as StarOffice, your browser, and your editor.
   3. Verify that banner pages, trailer pages, and security banners print correctly.

See Also

• Limit printer label range – How to Configure a Restricted Label Range for a Printer

• Prevent labeled output – Reducing Printing Restrictions in Trusted Extensions (Task Map)

• Use this zone as a print server – How to Enable a Trusted Extensions Client to Access a Printer

How to Configure a Zone for Single-Label Printing

Before You Begin

The zone must not be sharing an IP address with the global zone. You must be in the System Administrator role in the global zone.

1. Add a workspace.

   For details, see How to Add a Workspace at Your Minimum Label in Oracle Solaris Trusted Extensions User Guide.

2. Change the label of the new workspace to the label of the zone that will be the print server for that label.

   For details, see How to Change the Label of a Workspace in Oracle Solaris Trusted Extensions User Guide.

3. Define the characteristics of every connected printer.
   1. At the label of zone, start the Print Manager.

      By default, the “Use PPD” checkbox is selected. The system finds the appropriate driver for the printer.

   2. (Optional) To specify a different printer driver, do the following:
      1. Remove the check from “Use PPD”.
      2. Define the make and model of the printer that uses a different driver.

         In the Print Manager, you supply the values for the first two fields, then the Print Manager supplies the driver name.

         Printer Make   manufacturer
         Printer Model  manufacturer-part-number
         Printer Driver automatically filled in

4. Assign a printer model script to each printer that is connected to the print server.

   The model script activates the banner and trailer pages for the specified printer.

   For your choices of scripts, see Printer Model Scripts. Use the following command:

   $ lpadmin -p printer -m model

   The attached printers can print jobs only at the label of the zone.

5. Test the printer.

   ---

   Note - For security reasons, files with an administrative label, ADMIN_HIGH or ADMIN_LOW, print ADMIN_HIGH on the body of the printout. The banner and trailer pages are labeled with the highest label and compartments in the label_encodings file.

   ---

   As root and as a regular user, perform the following steps:

   1. Print plain files from the command line.
   2. Print files from your applications, such as StarOffice, your browser, and your editor.
   3. Verify that banner pages, trailer pages, and security banners print correctly.

See Also

• Prevent labeled output – Reducing Printing Restrictions in Trusted Extensions (Task Map)

• Use this zone as a print server – How to Enable a Trusted Extensions Client to Access a Printer

How to Enable a Trusted Extensions Client to Access a Printer

Initially, only the zone in which a print server was configured can print to the printers of that print server. The system administrator must explicitly add access to those printers for other zones and systems. The possibilities are as follows:

• For a global zone, add access to the printers that are connected to a global zone on a different system.

• For a labeled zone, add access to the printers that are connected to the global zone of its system.

• For a labeled zone, add access to a printer that a remote zone at the same label is configured for.

• For a labeled zone, add access to the printers that are connected to a global zone on a different system.

Before You Begin

A print server has been configured with a label range or a single label, and the printers that are connected to it have been configured. For details, see the following:

• How to Configure a Multilevel Print Server and Its Printers

• How to Configure a Zone for Single-Label Printing

• How to Assign a Label to an Unlabeled Print Server

You must be in the System Administrator role in the global zone, or be able to assume the role.

1. Complete the procedures that enable your systems to access a printer.
   • Configure the global zone on a system that is not a print server to use another system's global zone for printer access.
     1. On the system that does not have printer access, assume the System Administrator role.
     2. Add access to the printer that is connected to the Trusted Extensions print server.

        $ lpadmin -s printer

   • Configure a labeled zone to use its global zone for printer access.
     1. Change the label of the role workspace to the label of the labeled zone.

        For details, see How to Change the Label of a Workspace in Oracle Solaris Trusted Extensions User Guide.

     2. Add access to the printer.

        $ lpadmin -s printer

   • Configure a labeled zone to use another system's labeled zone for printer access.

     The labels of the zones must be identical.

     1. On the system that does not have printer access, assume the System Administrator role.
     2. Change the label of the role workspace to the label of the labeled zone.
     3. Add access to the printer that is connected to the print server of the remote labeled zone.

        $ lpadmin -s printer

   • Configure a labeled zone to use an unlabeled print server for printer access.

     The label of the zone must be identical to the label of the print server.

     1. On the system that does not have printer access, assume the System Administrator role.
     2. Change the label of the role workspace to the label of the labeled zone.

        For details, see How to Change the Label of a Workspace in Oracle Solaris Trusted Extensions User Guide.

     3. Add access to the printer that is connected to the arbitrarily labeled print server.

        $ lpadmin -s printer

2. Test the printers.

   ---

   Note - For security reasons, files with an administrative label, ADMIN_HIGH or ADMIN_LOW, print ADMIN_HIGH on the body of the printout. The banner and trailer pages are labeled with the highest label and compartments in the label_encodings file.

   ---

   On every client, test that printing works for root and roles in the global zone and for root, roles, and regular users in labeled zones.

   1. Print plain files from the command line.
   2. Print files from your applications, such as StarOffice, your browser, and your editor.
   3. Verify that banner pages, trailer pages, and security banners print correctly.

How to Configure a Restricted Label Range for a Printer

The default printer label range is ADMIN_LOW to ADMIN_HIGH. This procedure narrows the label range for a printer that is controlled by a Trusted Extensions print server.

Before You Begin

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

1. Start the Device Manager.

   Choose the Allocate Device option from the Trusted Path menu.

2. Click the Administration button to display the Device Administration dialog box.
3. Type a name for the new printer.

   If the printer is attached to your system, find the name of the printer.

4. Click the Configure button to display the Device Configuration dialog box.
5. Change the printer's label range.
   1. Click the Min Label button to change the minimum label.

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

   2. Click the Max Label button to change the maximum label.
6. Save the changes.
   1. Click OK in the Configuration dialog box.
   2. Click OK in the Administration dialog box.
7. Close the Device Manager.