Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ipropd-master(8) [netbsd man page]

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

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/ 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

kprop(1M)						  System Administration Commands						 kprop(1M)

kprop - Kerberos database propagation program SYNOPSIS
/usr/lib/krb5/kprop [-d] [-f file] [-p port-number] [-r realm] [-s keytab] [host] DESCRIPTION
kprop is a command-line utility used for propagating a Kerberos database from a master KDC to a slave KDC. This command must be run on the master KDC. See the Solaris System Administration Guide, Vol. 6 on how to set up periodic propagation between the master KDC and slave KDCs. To propagate a Kerberos database, the following conditions must be met: o The slave KDCs must have an /etc/krb5/kpropd.acl file that contains the principals for the master KDC and all the slave KDCs. o A keytab containing a host principal entry must exist on each slave KDC. o The database to be propagated must be dumped to a file using kdb5_util(1M). OPTIONS
The following options are supported: -d Enable debug mode. Default is debug mode disabled. -f file File to be sent to the slave KDC. Default is the /var/krb5/slave_datatrans file. -p port-number Propagate port-number. Default is port 754. -r realm Realm where propagation will occur. Default realm is the local realm. -s keytab Location of the keytab. Default location is /etc/krb5/krb5.keytab. OPERANDS
The following operands are supported: host Name of the slave KDC. EXAMPLES
Example 1 Propagating the Kerberos Database The following example propagates the Kerberos database from the /tmp/slave_data file to the slave KDC london. The machine london must have a host principal keytab entry and the kpropd.acl file must contain an entry for the all the KDCs. # kprop -f /tmp/slave_data london FILES
/etc/krb5/kpropd.acl List of principals of all the KDCs; resides on each slave KDC. /etc/krb5/krb5.keytab Keytab for Kerberos clients. /var/krb5/slave_datatrans Kerberos database propagated to the KDC slaves. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkdcu | +-----------------------------+-----------------------------+ SEE ALSO
kpasswd(1), svcs(1), gkadmin(1M), inetadm(1M), inetd(1M), kadmind(1M), kadmin.local(1M), kdb5_util(1M), svcadm(1M), kadm5.acl(4), kdc.conf(4), attributes(5), kerberos(5), smf(5) SunOS 5.11 14 Nov 2005 kprop(1M)
Man Page