Skip Navigation Links | |
Exit Print View | |
Trusted Extensions Administrator's Procedures Oracle Solaris 10 1/13 Information Library |
1. Trusted Extensions Administration Concepts
2. Trusted Extensions Administration Tools
3. Getting Started as a Trusted Extensions Administrator (Tasks)
4. Security Requirements on a Trusted Extensions System (Overview)
5. Administering Security Requirements in Trusted Extensions (Tasks)
6. Users, Rights, and Roles in Trusted Extensions (Overview)
7. Managing Users, Rights, and Roles in Trusted Extensions (Tasks)
8. Remote Administration in Trusted Extensions (Tasks)
9. Trusted Extensions and LDAP (Overview)
10. Managing Zones in Trusted Extensions (Tasks)
11. Managing and Mounting Files in Trusted Extensions (Tasks)
12. Trusted Networking (Overview)
13. Managing Networks in Trusted Extensions (Tasks)
14. Multilevel Mail in Trusted Extensions (Overview)
15. Managing Labeled Printing (Tasks)
16. Devices in Trusted Extensions (Overview)
17. Managing Devices for Trusted Extensions (Tasks)
18. Trusted Extensions Auditing (Overview)
19. Software Management in Trusted Extensions (Tasks)
A. Quick Reference to Trusted Extensions Administration
In Trusted Extensions, the System Administrator role sets up and administers mail servers according to instructions in the Oracle Solaris System Administration Guide: Advanced Administration and Oracle Solaris Administration: IP Services. In addition, the security administrator determines how Trusted Extensions mail features need to be configured.
The following aspects of managing mail are specific to Trusted Extensions:
The .mailrc file is at a user's minimum label.
Therefore, users who work at multiple labels do not have a .mailrc file at the higher labels, unless they copy or link the .mailrc file in their minimum-label directory to each higher directory.
The Security Administrator role or the individual user can add the .mailrc file to either .copy_files or .link_files. For a description of these files, see the updatehome(1M) man page. For configuration suggestions, see .copy_files and .link_files Files.
Your mail reader can run at every label on a system. Some configuration is required to connect a mail client to the server.
For example, to use Mozilla mail for multilevel mail requires that you configure a Mozilla mail client at each label to specify the mail server. The mail server could be the same or different for each label, but the server must be specified.
The Mailing Lists tool in the Solaris Management Console manages mail aliases.
Depending on the scope of the selected Solaris Management Console toolbox, you can update the local /etc/aliases file or the LDAP entry on the Oracle Directory Server Enterprise Edition.
Trusted Extensions software checks host and user labels before sending or forwarding mail.
The software checks that the mail is within the accreditation range of the host. The checks are described in this list and in Chapter 13, Managing Networks in Trusted Extensions (Tasks).
The software checks that the mail is between the account's clearance and minimum label.
Users can read email that is received within their accreditation range. During a session, users can read mail only at their current label.
To contact regular user by email, an administrative role must send mail from a workspace that is at a label that the user can read. The user's default label is usually a good choice.