xref: /titanic_44/usr/src/man/man1m/tnchkdb.1m (revision 686c0471389a2f92c1e43b38e1b97771bee482ab)
te
Copyright (c) 2006, Sun Microsystems, Inc. All Rights Reserved.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
tnchkdb 1M "20 Jul 2007" "SunOS 5.11" "System Administration Commands"
NAME
tnchkdb - check file syntax of trusted network databases
SYNOPSIS

/usr/sbin/tnchkdb [-h path] [-t path] [-z path]
DESCRIPTION

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.

OPTIONS

-h [ path ]

Check path for proper tnrhdb syntax. If path is not specified, then check /etc/security/tsol/tnrhdb.

-t [ path ]

Check path for proper tnrhtp syntax. If path is not specified, then check /etc/security/tsol/tnrhtp.

-z [ path ]

Check path for proper tnzonecfg syntax. If path is not specified, then check /etc/security/tsol/tnzonecfg.

EXAMPLES

Example 1 Sample Error Message

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 ...
FILES

/etc/security/tsol/tnrhdb

Trusted network remote-host database

/etc/security/tsol/tnrhtp

Trusted network remote-host templates

/etc/security/tsol/tnzonecfg

Trusted zone configuration database

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPEATTRIBUTE VALUE
Interface StabilitySee below.

The command line is Committed. The output is Uncommitted.

SEE ALSO

tnd(1M), tnctl(1M), attributes(5)

How to Check the Syntax of Trusted Network Databases in Solaris Trusted Extensions Administrator's Procedures

NOTES

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.