Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

iprop(8) [netbsd man page]

IPROP(8)						    BSD System Manager's Manual 						  IPROP(8)

NAME
iprop, ipropd-master, ipropd-slave -- propagate changes to a Heimdal Kerberos master KDC to slave KDCs SYNOPSIS
ipropd-master [-c string | --config-file=string] [-r string | --realm=string] [-k kspec | --keytab=kspec] [-d file | --database=file] [--slave-stats-file=file] [--time-missing=time] [--time-gone=time] [--detach] [--version] [--help] ipropd-slave [-c string | --config-file=string] [-r string | --realm=string] [-k kspec | --keytab=kspec] [--time-lost=time] [--detach] [--version] [--help] master DESCRIPTION
ipropd-master is used to propagate changes to a Heimdal Kerberos database from the master Kerberos server on which it runs to slave Kerberos servers running ipropd-slave. The slaves are specified by the contents of the slaves file in the KDC's database directory, e.g. /var/heimdal/slaves. This has principals one per-line of the form iprop/slave@REALM where slave is the hostname of the slave server in the given REALM, e.g. iprop/kerberos-1.example.com@EXAMPLE.COM On a slave, the argument master specifies the hostname of the master server from which to receive updates. In contrast to hprop(8), which sends the whole database to the slaves regularly, iprop normally sends only the changes as they happen on the master. The master keeps track of all the changes by assigning a version number to every change to the database. The slaves know which was the latest version they saw, and in this way it can be determined if they are in sync or not. A log of all the changes is kept on the mas- ter. When a slave is at an older version than the oldest one in the log, the whole database has to be sent. The changes are propagated over a secure channel (on port 2121 by default). This should normally be defined as ``iprop/tcp'' in /etc/services or another source of the services database. The master and slaves must each have access to a keytab with keys for the iprop service principal on the local host. There is a keep-alive feature logged in the master's slave-stats file (e.g. /var/heimdal/slave-stats). Supported options for ipropd-master: -c string, --config-file=string -r string, --realm=string -k kspec, --keytab=kspec keytab to get authentication from -d file, --database=file Database (default per KDC) --slave-stats-file=file file for slave status information --time-missing=time time before slave is polled for presence (default 2 min) --time-gone=time time of inactivity after which a slave is considered gone (default 5 min) --detach detach from console --version --help Supported options for ipropd-slave: -c string, --config-file=string -r string, --realm=string -k kspec, --keytab=kspec keytab to get authentication from --time-lost=time time before server is considered lost (default 5 min) --detach detach from console --version --help Time arguments for the relevant options above may be specified in forms like 5 min, 300 s, or simply a number of seconds. FILES
slaves, slave-stats in the database directory. SEE ALSO
krb5.conf(5), hprop(8), hpropd(8), iprop-log(8), kdc(8). BSD
May 24, 2005 BSD

Check Out this Related Man Page

HPROP(8)						    BSD System Manager's Manual 						  HPROP(8)

NAME
hprop -- propagate the KDC database SYNOPSIS
hprop [-m file | --master-key=file] [-d file | --database=file] [--source=heimdal|mit-dump] [-r string | --v4-realm=string] [-c cell | --cell=cell] [-k keytab | --keytab=keytab] [-R string | --v5-realm=string] [-D | --decrypt] [-E | --encrypt] [-n | --stdout] [-v | --verbose] [--version] [-h | --help] [host[:port]] ... DESCRIPTION
hprop takes a principal database in a specified format and converts it into a stream of Heimdal database records. This stream can either be written to standard out, or (more commonly) be propagated to a hpropd(8) server running on a different machine. If propagating, it connects to all hosts specified on the command by opening a TCP connection to port 754 (service hprop) and sends the data- base in encrypted form. Supported options: -m file, --master-key=file Where to find the master key to encrypt or decrypt keys with. -d file, --database=file The database to be propagated. --source=heimdal|mit-dump|krb4-dump|kaserver Specifies the type of the source database. Alternatives include: heimdal a Heimdal database mit-dump a MIT Kerberos 5 dump file +.It Fl k Ar keytab , Fl Fl keytab= Ns Ar keytab The keytab to use for fetching the key to be used for authenticating to the propaga- tion daemon(s). The key hprop/hostname is used from this keytab. The default is to fetch the key from the KDC database. -R string, --v5-realm=string Local realm override. -D, --decrypt The encryption keys in the database can either be in clear, or encrypted with a master key. This option transmits the database with unencrypted keys. -E, --encrypt This option transmits the database with encrypted keys. -n, --stdout Dump the database on stdout, in a format that can be fed to hpropd. EXAMPLES
The following will propagate a database to another machine (which should run hpropd(8)): $ hprop slave-1 slave-2 SEE ALSO
hpropd(8) HEIMDAL
December 8, 2004 HEIMDAL

Featured Tech Videos