|Skip Navigation Links|
|Exit Print View|
|Trusted Extensions Configuration and Administration Oracle Solaris 11 Information Library|
NFS mounts in Trusted Extensions are similar to Oracle Solaris mounts. The differences occur in the enforcement of MAC policy. Also, the txzonemgr script assumes that home directories are mounted as /export/home.
NFS shares in Trusted Extensions are similar to Oracle Solaris shares in a global zone. However, the sharing of a labeled zone on a multilevel system is unique to Trusted Extensions:
Shares and mounts in the global zone – Sharing and mounting files in the global zone of a Trusted Extensions system is almost identical to the procedure in Oracle Solaris. For mounting files, the automounter, and the mount command can be used. For sharing files, the sharenfs property of ZFS datasets is used.
Mounts in labeled zones – Mounting files in labeled zones in Trusted Extensions is almost identical to mounting files in non-global zones in Oracle Solaris. For mounting files, the automounter and the mount command can be used. In Trusted Extensions, a unique auto_home_zone-name configuration file exists for each labeled zone.
Shares in labeled zones – Files in a labeled zone can be shared at the label of the zone by using the ZFS share properties. For more discussion, see Global Zone Processes and Labeled Zones.
Labels affect which files can be mounted. Files are shared and mounted at a particular label.
For a Trusted Extensions system to mount a file system on another Trusted Extensions system, the server and the client must have compatible remote host templates of type cipso.
For a Trusted Extensions client to write to a file system that is NFS-mounted, the file system must be mounted with read-write permissions and be at the same label as the client.
For a Trusted Extensions system to mount a file system from an unlabeled system, the single label that is assigned to the unlabeled system by the Trusted Extensions system must match the label of the Trusted Extensions system.
Similarly, for a labeled zone to mount a file system from an unlabeled system, the single label that is assigned to the unlabeled system by the Trusted Extensions system must match the label of the labeled zone.
File systems whose labels differ from the mounting zone and are mounted with LOFS can be viewed, but cannot be modified. For details on NFS mounts, see Access to NFS Mounted File Systems in Trusted Extensions.
Labels also affect which directories and files can be viewed. By default, lower-level objects are available in a user's environment. Therefore, in the default configuration, a regular user can view files that are in a zone at a lower level than the user's current level. For example, users can see their lower-level home directories from a higher label. For details, see Home Directory Creation in Trusted Extensions.
If site security forbids the viewing of lower-level objects, you can hide lower-level file systems from the user. For details, see How to Disable the Mounting of Lower-Level Files.
The mount policy in Trusted Extensions has no MAC overrides. Mounted files that are visible at a lower label can never be modified by a higher-label process. This MAC policy is also in effect in the global zone. A global zone ADMIN_HIGH process cannot modify an NFS-mounted file at a lower label, such as a PUBLIC file or an ADMIN_LOW file. MAC policies enforce the default configuration and are invisible to regular users. Regular users cannot see objects unless they have MAC access to them.