Provided by: pkcipe_1.5.4free-9_i386
pkcipe - PK implementation for CIPE
pkcipe [OPTIONS] NAME
pkcipe is a helper tool to set up VPNs using CIPE.
Each machine in the VPN has an identity (such as its host name) and a
public/private RSA key pair. The private key is stored in
/etc/cipe/identity.priv. For every allowed CIPE connection, the public
key of the other part is stored, along with configuration parameters,
in /etc/cipe/pk/NAME (where NAME is the identity of the other part).
Thus storing a public key gives permission to connect, similar to the
SSH package (it is important to know how this works to not open holes).
For a quick overview on how to set up pkcipe on a Debian system, please
refer to /usr/share/doc/pkcipe/README.Debian.gz. There is also more
information on how to invoke pkcipe in /usr/share/doc/pkcipe/README.gz.
A summary of the pkcipe options is included below.
-i To be invoked from inetd. Incompatible with -c.
To connect to host:port. Incompatible with -i.
Gives location of private key file.
Routing IP address. Only for unusual cases, s.b.
-E Use stderr instead of syslog. (Debugging only, incompatible with
Fall back to given protocol level.
This manual page was written by Sam Hocevar <firstname.lastname@example.org> for the
Debian system (but may be used by others).
Mar 28, 2003 PKCIPE(8)