tnchkdb - check file syntax of trusted network databases
/usr/sbin/tnchkdb [-h path] [-t path] [-z path]
tnchkdb checks the syntax of the tnrhtp, tnrhdb, and tnzonecfg databases. By default, the path for each file is:
You can specify an alternate path for any or all of the files by specifying that path on the command line by using the –h (tnrhdb), –t (tnrhtp) and –z (tnzonecfg) options. The options are useful when testing a set of modified files before installing the files as new system databases.
All three database files are checked for integrity. tnchkdb returns an exit status of 0 if all of the files are syntactically and, to the extent possible, semantically correct. If one or more files have errors, then an exit status of 1 is returned. If there are command line problems, such as an unreadable file, an exit status of 2 is returned. Errors are written to standard error.
To avoid cascading errors, when there are errors in tnrhtp, the template names in tnrhdb are not validated.
tnchkdb can be run at any label, but the standard /etc/security/tsol files are visible only in the global zone.
Check path for proper tnrhdb syntax. If path is not specified, then check /etc/security/tsol/tnrhdb.
Check path for proper tnrhtp syntax. If path is not specified, then check /etc/security/tsol/tnrhtp.
Check path for proper tnzonecfg syntax. If path is not specified, then check /etc/security/tsol/tnzonecfg.
The tnchkdb command checks for CIPSO errors. In this example, the admin_low template has an incorrect value of ADMIN_HIGH for its default label.
# tnchkdb checking /etc/security/tsol/tnrhtp ... tnchkdb: def_label classification 7fff is invalid for cipso labels: line 14 entry admin_low tnchkdb: def_label compartments 241-256 must be zero for cipso labels: line 14 entry admin_low checking /etc/security/tsol/tnrhdb ... checking /etc/security/tsol/tnzonecfg ...
Trusted network remote-host database
Trusted network remote-host templates
Trusted zone configuration database
See attributes(5) for descriptions of the following attributes:
The command line is Committed. The output is Uncommitted.
The functionality described on this manual page is available only if the system is configured with Trusted Extensions.
It is possible to have inconsistent but valid configurations of tnrhtp and tnrhdb when LDAP is used to supply missing templates.