Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ipsec_newhostkey(8) [centos man page]

IPSEC_RANBITS(8)						Executable programs						  IPSEC_RANBITS(8)

NAME
ipsec_newhostkey - generate a new raw RSA authentication key for a host SYNOPSIS
ipsec newhostkey [[--configdirnssdbdir] | [--password password]] [[--quiet] | [--verbose]] [--bits bits] [--random device] [--hostname hostname] [--output filename] DESCRIPTION
newhostkey outputs (into filename, which can be '-' for standard output) an RSA private key suitable for this host, in /etc/ipsec.secrets format (see ipsec.secrets(5)) using the --quiet option per default. The --output option is mandatory. The specified filename is created under umask 077 if nonexistent; if it already exists and is non-empty, a warning message about that is sent to standard error, and the output is appended to the file. The --quiet option suppresses both the rsasigkey narrative and the existing-file warning message. When compiled with NSS support (the default), --configdir specifies the nss configuration directory where the certificate key, and modsec databases reside. There is no default value, though /etc/ipsec.d might be sensible choice. When compiled with NSS support (the default), --password specifies a module authentication password that may be required if FIPS mode is enabled The --bits option specifies the number of bits in the RSA key; the current default is a random (multiple of 16) value between 3072 and 4096. The minimum allowed is 2172. The --random is used to specify the random device (default /dev/random used to seed the crypto library RNG. The --hostname option is passed through to rsasigkey to tell it what host name to label the output with (via its --hostname option). The output format is that of rsasigkey, with bracketing added to complete the ipsec.secrets format. In the usual case, where ipsec.secrets contains only the hostas own private key, the output of newhostkey is sufficient as a complete ipsec.secrets file. FILES
/dev/random, /dev/urandom SEE ALSO
ipsec_rsasigkey(8), ipsec.secrets(5) HISTORY
Originally written for the Linux FreeS/WAN project <http://www.freeswan.org> by Henry Spencer. Updated by Paul Wouters BUGS
As with rsasigkey, the run time is difficult to predict, since depletion of the systemas randomness pool can cause arbitrarily long waits for random bits, and the prime-number searches can also take unpre dictable (and potentially large) amounts of CPU time. See ipsec_rsasigkey(8) . A higher-level tool which could handle the clerical details of changing to a new key would be helpful. AUTHOR
Paul Wouters placeholder to suppress warning libreswan 09/06/2013 IPSEC_RANBITS(8)

Check Out this Related Man Page

IPSEC_ADDCONN(8)						Executable programs						  IPSEC_ADDCONN(8)

NAME
ipsec_addconn - load a given policy into the pluto IKE daemon SYNOPSIS
ipsec addconn --configsetup [--rootdir dir] [--config filename] [--ctlbase socketfile] [--verbose] [--noexport] [--warningsfatal] ipsec addconn --liststack [--rootdir dir] [--config filename] [--ctlbase socketfile] [--verbose] [--noexport] [--warningsfatal] ipsec addconn --checkconfig [--rootdir dir] [--config filename] [--ctlbase socketfile] [--verbose] [--warningsfatal] ipsec addconn --autoall [--rootdir dir] [--config filename] [--ctlbase socketfile] [--verbose] [--warningsfatal] [--defaultroute addr] [--defaultroutenexthop addr] ipsec addconn [--rootdir dir] [--config filename] [--ctlbase socketfile] [--verbose] [--warningsfatal] [--defaultroute addr] [--defaultroutenexthop addr] name1 [name2 ..] ipsec addconn [--listall] [--liststart] [--listroute] [--listadd] [--listignore] [--rootdir dir] [--config filename] [--ctlbase socketfile] [--verbose] [--warningsfatal] ipsec addconn --help DESCRIPTION
ipsec addconn takes a config file (or stdin) containing the format of ipsec.conf, or the format of individual "conn" sections, and uses that information to load named or all connections defined in that configuration file into the running libreswan pluto IKE daemon. If no configuration file is specified, the default configuration file is used. If no pluto socket is specified, the default socket location will be used. When --addall is used, all connections defined in the config file will be operated on. Otherwise, only the specified connection names will be affected. When addcon is run, connections that have the auto= option set to add, start or route will be loaded, routed or initiated. If a connection was loaded or initiated already, it will be replaced. When --configsetup is specified, the configuration file is parsed for the config setup section and printed to the terminal usable as a shell script. These are prefaced with export unless --noexport is specified. When --checkconfig is specified, the configuration file is parsed and all sections are checked for correct syntax. If an error is found, information about it is printed to the terminal. When --listroute or --liststart is specified, no connections are added or replaced, only shown. This command can be used to verify which connections the addcon command would act upon, without actually performing any action. HISTORY
Man page written for the Libreswan project <http://www.libreswan.org/> by Paul Wouters AUTHOR
Paul Wouters placeholder to suppress warning libreswan 12/16/2012 IPSEC_ADDCONN(8)
Man Page

Featured Tech Videos