After installing and customizing an Oracle Solaris 11 non-global (solaris brand) zone, you execute commands:
# zonecfg --z myzone 'set file-mac-profile=fixed-configuration'
# zoneadm --z myzone reboot
What is the impact of making this specific change?
Through the zonecfg utility, the file-mac-profile can be set to one of the following values (see note below). All of the profiles except none will cause the /var/pkg directory and its contents to be read-only from inside the zone.
* none
Standard, read-write, non-global zone, with no additional protection beyond the existing zones boundaries. Setting the value to none is equivalent to not setting file-mac-profile property.
* strict
* fixed-configuration
Permits updates to /var/* directories, with the exception of directories that contain system configuration components.
IPS packages, including new packages, cannot be installed.
Persistently enabled SMF services are fixed.
SMF manifests cannot be added from the default locations.
Logging and auditing configuration files can be local. syslog and audit configuration are fixed.
* flexible-configuration
Note:
zonecfg file-mac-profile Property
By default, the zonecfg file-mac-profile property is not set in a non-global zone. A zone is configured to have a writable root dataset.
In a solaris read-only zone, the file-mac-profile property is used to configure a read-only zone root. A read---only root restricts access to the runtime environment from inside the zone.
Currently there are no comments in this discussion, be the first to comment!