opendkim-genkey(8) [debian man page]

opendkim-genkey(8)					      System Manager's Manual						opendkim-genkey(8)

NAME

       opendkim-genkey - DKIM filter key generation tool

SYNOPSIS

       opendkim-genkey [options]

DESCRIPTION

       opendkim-genkey	generates  (1)	a  private key for signing messages using opendkim(8) and (2) a DNS TXT record suitable for inclusion in a
       zone file which publishes the matching public key for use by remote DKIM verifiers.

       The filenames of these are based on the selector (see below); the private key will have a suffix of ".private" and the TXT record will have
       a suffix of ".txt".

OPTIONS

       -a     Appends  the  domain  name (see -d below) to the label in the generated TXT record, followed by a trailing period.  By default it is
	      assumed the domain name is implicit from the context of the zone file, and is therefore not included in the output.

       -b bits
	      Specifies the size of the key, in bits, to be generated.	The default is 1024 which is the value recommended by the DKIM	specifica-
	      tion.

       -d domain
	      Names  the  domain  which  will  use this key for signing.  Currently only used in a comment in the TXT record file.  The default is
	      "example.com".

       -D directory
	      Instructs the tool to change to the named directory prior to creating files.  By default the current directory is used.

       -h algorithms
	      Specifies a list of hash algorithms which can be used with this key.  By default all hash algorithms are allowed.

       -n note
	      Includes arbitrary note text in the key record.  By default, no such text is included.

       -r     Restricts the key for use in e-mail signing only.  The default is to allow the key to be used for any service.

       -s selector
	      Specifies the selector, or name, of the key pair generated.  The default is "default".

       -S     Disallows subdomain signing by this key.	By default the key record will be generated such that verifiers are told subdomain signing
	      is permitted.

       -t     Indicates the generated key record should be tagged such that verifiers are aware DKIM is in test at the signing domain.

NOTES

       Requires that the openssl(8) binary be installed and in the executing shell's search path.

VERSION

       This man page covers the version of opendkim-genkey that shipped with version 2.6.8 of OpenDKIM.

COPYRIGHT

       Copyright (c) 2007, 2008 Sendmail, Inc. and its suppliers.  All rights reserved.

       Copyright (c) 2009, 2011, 2012, The OpenDKIM Project.  All rights reserved.

SEE ALSO

       opendkim(8), openssl(8)

       RFC6376 - DomainKeys Identified Mail

							       The OpenDKIM Project						opendkim-genkey(8)

GENKEY(1)						      Cryptography Utilities							 GENKEY(1)

NAME

       genkey - generate SSL certificates and certificate requests

SYNOPSIS

       genkey [--test] [--days count] [[--genreq] | [--makeca] | [--nss] | [--renew] | [--cacert]] {hostname}

DESCRIPTION

       genkey is an interactive command-line tool which can be used to generate SSL certificates or Certificate Signing Requests (CSR). Generated
       certificates are stored in the directory /etc/pki/tls/certs/, and the corresponding private key in /etc/pki/tls/private/.

       When using mod_nss the private key is stored in the nss database. Consult the nss.conf file in /etc/httpd/conf.d/ for the location of the
       database.

       genkey will prompt for the size of key desired; whether or not to generate a CSR; whether or not an encrypted private key is desired; the
       certificate subject DN details.

       genkey generates random data for the private key using the truerand library and also by prompting the user for entry of random text.

       nss indicates that mod_nss database should be used to store keys and certificates.

OPTIONS

       --makeca
	   Generate a Certificate Authority keypair and certificate.

       --genreq
	   Generate a Certificate Signing Request for an existing private key, which can be submitted to a CA (for example, for renewal).

       --renew
	   Used with --genreq to indicate a renewal, the existing keypair will be used. Certs and keys must reside in the nss database, therefore
	   --nss is also required. Pem file based cert renewal is not currently supported.

       --cacert
	   The certificate renewal is for a CA, needed for openssl certs only.

       --days count
	   When generating a self-signed certificate, specify that the number of days for which the certificate is valid be count rather than the
	   default value of 30.

       --test
	   For test purposes only; omit the slow process of generating random data.

EXAMPLES

       The following example will create a self-signed certificate and private key for the hostname www.example.com:

		   # genkey --days 120 www.example.com

       The following example will create a self-signed certificate and private key for the hostname www.nssexample.com which will be stored in
       cert and key in the nss database. If no nickname is given the tool will extract it from mod_nss's nss configuration file.

		   # genkey --days --nss 120 www.nssexample.com

       The following example will generate a certificate signing request for a new mod_nss style cert specified by its nickname, Server-Cert:

		   # genkey --genreq --nss --days 120 Server-Cert

       The following example will generate a certificate signing request for the renewal of an existing mod_nss cert specified by its nickname,
       Server-Cert:

		   # genkey --genreq --renew --nss --days 120 Server-Cert

FILES

       /etc/pki/tls/openssl.cnf

SEE ALSO

       certwatch(1), keyrand(1)

crypto-utils 2.4.1						    9 June 2014 							 GENKEY(1)