#++ # NAME # postfix-tls 1 # SUMMARY # Postfix TLS management # SYNOPSIS # \fBpostfix tls\fR \fIsubcommand\fR # DESCRIPTION # The "\fBpostfix tls \fIsubcommand\fR" feature enables # opportunistic TLS in the Postfix SMTP client or server, and # manages Postfix SMTP server private keys and certificates.
java.lang.NullPointerException # The following subcommands are available: # .IP "\fBenable-client\fR [\fB-r \fIrandsource\fR]" # Enable opportunistic TLS in the Postfix SMTP client, if all # SMTP client TLS settings are at their default values. # Otherwise, suggest parameter settings without making any # changes. # .sp # Specify \fIrandsource\fR to update the value of the # \fBtls_random_source\fR configuration parameter (typically, # /dev/urandom). Prepend \fBdev:\fR to device paths or # \fBegd:\fR to EGD socket paths. # .sp # See also the \fBall-default-client\fR subcommand. # .IP "\fBenable-server\fR [\fB-r \fIrandsource\fR] [\fB-a \fIalgorithm\fR] [\fB-b \fIbits\fR] [\fIhostname\fB...\fR]" # Create a newprivate key and self-signed server certificate # and enable opportunistic TLS in the Postfix SMTP server, # if all SMTP server TLS settings are at their default values. # Otherwise, suggest parameter settings without making any # changes. # .sp # The \fIrandsource\fR parameter is as with \fBenable-client\fR # above, and the remaining options are as with \fBnew-server-key\fR # below. # .sp # See also the \fBall-default-server\fR subcommand. # .IP "\fBnew-server-key\fR [\fB-a \fIalgorithm\fR] [\fB-b \fIbits\fR] [\fIhostname\fB...\fR]" # Create a newprivate key and self-signed server certificate, # but donot deploy them. Log and display commands to deploy # the new key and corresponding certificate. Also log and # display commands to output a corresponding CSR or TLSA # records which may be needed to obtain a CA certificate or # to update DNS before the new key can be deployed. # .sp # The \fIalgorithm\fR defaults to \fBrsa\fR, and \fIbits\fR # defaults to 2048. If you choose the \fBecdsa\fR \fIalgorithm\fR # then \fIbits\fR will be an EC curve name (by default # \fBsecp256r1\fR, also known as prime256v1). Curves other # than \fBsecp256r1\fR, \fBsecp384r1\fR or \fBsecp521r1\fR # are unlikely to be widely interoperable. When generating # EC keys, use one of these three. DSA keys are obsolete and # are not supported. # .sp # Note: ECDSA support requires OpenSSL 1.0.0or later and may # not be available on your system. Not all client systems # will support ECDSA, so you'll generally want to deploy both # RSA and ECDSA certificates to make use of ECDSA with # compatible clients and RSA with the rest. If you want to # deploy certificate chains with intermediate CAs for both # RSA and ECDSA, you'll want at least OpenSSL 1.0.2, as earlier # versions may not handle multiple chain files correctly. # .sp # The first \fIhostname\fR argument will be the \fBCommonName\fR # of both the subject and issuer of the self-signed certificate. # It, and any additional \fIhostname\fR arguments, will also # be listed as DNS alternative names in the certificate. If # no \fIhostname\fR is provided the value of the \fBmyhostname\fR # main.cf parameter will be used. # .sp # For RSA, the generated private key and certificate files # are named \fBkey-\fIyyyymmdd-hhmmss\fB.pem\fR and # \fBcert-\fIyyyymmdd-hhmmss\fB.pem\fR, where \fIyyyymmdd\fR # is the calendar date and \fIhhmmss\fR is the time of day # in UTC. For ECDSA, the file names start with \fBeckey-\fR # and \fBeccert-\fR instead of \fBkey-\fR and \fBcert-\fR # respectively. # .sp # Before deploying the new key and certificate with DANE, # update the DNS with new DANE TLSA records, then wait for # secondary nameservers to update and then for stale records # in remote DNS caches to expire. # .sp # Before deploying a new CA certificate make sure to include # all the required intermediate issuing CA certificates in # the certificate chain file. The server certificate must # be the first certificate in the chain file. Overwrite and # deploy the file with the original self-signed certificate # that was generated together with the key. # .IP "\fBnew-server-cert\fR [\fB-a \fIalgorithm\fR] [\fB-b \fIbits\fR] [\fIhostname\fB...\fR]" # This is just like \fBnew-server-key\fR except that, rather # than generating a newprivate key, any currently deployed # private key is copied to the new key file. Thus if you're # publishing DANE TLSA "3 1 1"or"3 1 2" records, there is # no need to update DNS records. The \fIalgorithm\fR and # \fIbits\fR arguments are used only if no key of the same # algorithm is already configured. # .sp # This command is rarely needed, because the self-signed # certificates generated have a 100-year nominal expiration # time. The underlying public key algorithms may well be # obsoleted by quantum computers long before then. # .sp # The most plausible reason forusingthis command is when # the system hostname changes, and you'd like the name in the # certificate to match the new hostname (not required for # DANE "3 1 1", but some needlessly picky non-DANE opportunistic # TLS clients may log warnings or even refuse to communicate). # .IP "\fBdeploy-server-cert \fIcertfile\fB \fIkeyfile\fR" # This subcommand deploys the certificates in \fIcertfile\fR # andprivate key in \fIkeyfile\fR (which are typically # generated by the commands above, which will also log and # display the full command needed to deploy the generated key # and certificate). After the new certificate and key are # deployed any obsolete keys and certificates may be removed # by hand. The \fIkeyfile\fR and \fIcertfile\fR filenames # may be relative to the Postfix configuration directory. # .IP "\fBoutput-server-csr\fR [\fB-k \fIkeyfile\fR] [\fIhostname\fB...\fR]" # Write to stdout a certificate signing request (CSR) for the # specified \fIkeyfile\fR. # .sp # Instead of an absolute pathname or a pathname relative to # $config_directory, \fIkeyfile\fR may specify one of the # supported key algorithm names (see "\fBpostconf -T # public-key-algorithms\fR"). In that case, the corresponding # setting from main.cf is used to locate the \fIkeyfile\fR. # The default \fIkeyfile\fR value is \fBrsa\fR. # .sp # Zero or more \fIhostname\fR values can be specified. The # default \fIhostname\fR is the value of \fBmyhostname\fR # main.cf parameter. # .IP "\fBoutput-server-tlsa\fR [\fB-h \fIhostname\fR] [\fIkeyfile\fB...\fR]" # Write to stdout a DANE TLSA RRset suitable for a port 25 # SMTP server on host \fIhostname\fR with keys from any of # the specified \fIkeyfile\fR values. The default \fIhostname\fR # is the value of the \fBmyhostname\fR main.cf parameter. # .sp # Instead of absolute pathnames or pathnames relative to # $config_directory, the \fIkeyfile\fR list may specify # names of supported public key algorithms (see "\fBpostconf # -T public-key-algorithms\fR"). In that case, the actual # \fIkeyfile\fR list uses the values of the corresponding # Postfix server TLS key file parameters. If a parameter # value is empty or equal to \fBnone\fR, then no TLSA record # is output for that algorithm. # .sp # The default \fIkeyfile\fR list consists of the two supported # algorithms \fBrsa\fR and \fBecdsa\fR. # AUXILIARY COMMANDS # .IP "\fBall-default-client\fR" # Exit with status 0 (success) if all SMTP client TLS settings are # at their default values. Otherwise, exit with a non-zero status. # This is typically used as follows: # .sp # \fBpostfix tls all-default-client && # postfix tls enable-client\fR # .IP "\fBall-default-server\fR" # Exit with status 0 (success) if all SMTP server TLS settings are # at their default values. Otherwise, exit with a non-zero status. # This is typically used as follows: # .sp # \fBpostfix tls all-default-server && # postfix tls enable-server\fR # CONFIGURATION PARAMETERS # .ad # .fi # The "\fBpostfix tls \fIsubcommand\fR" feature reads # or updates the following configuration parameters. # .IP "\fBcommand_directory (see 'postconf -d' output)\fR" # The location of all postfix administrative commands. # .IP "\fBconfig_directory (see 'postconf -d' output)\fR" # The default location of the Postfix main.cf and master.cf # configuration files. # .IP "\fBopenssl_path (openssl)\fR" # The location of the OpenSSL command line program \fBopenssl\fR(1). # .IP "\fBsmtp_tls_loglevel (0)\fR" # Enable additional Postfix SMTP client logging of TLS activity. # .IP "\fBsmtp_tls_security_level (Postfix >= 3.11: may; Postfix < 3.11: empty)\fR" # The default SMTP TLS security level for the Postfix SMTP client. # .IP "\fBsmtp_tls_session_cache_database (empty)\fR" # Name of the file containing the optional Postfix SMTP client # TLS session cache. # .IP "\fBsmtpd_tls_cert_file (empty)\fR" # File with the Postfix SMTP server RSA certificate in PEM format. # .IP "\fBsmtpd_tls_eccert_file (empty)\fR" # File with the Postfix SMTP server ECDSA certificate in PEM format. # .IP "\fBsmtpd_tls_eckey_file ($smtpd_tls_eccert_file)\fR" # File with the Postfix SMTP server ECDSA private key in PEM format. # .IP "\fBsmtpd_tls_key_file ($smtpd_tls_cert_file)\fR" # File with the Postfix SMTP server RSA private key in PEM format. # .IP "\fBsmtpd_tls_loglevel (0)\fR" # Enable additional Postfix SMTP server logging of TLS activity. # .IP "\fBsmtpd_tls_received_header (no)\fR" # Request that the Postfix SMTP server produces Received: message # headers that include information about the protocol and cipher used, # as well as the remote SMTP client CommonName and client certificate issuer # CommonName. # .IP "\fBsmtpd_tls_security_level (empty)\fR" # The SMTP TLS security level for the Postfix SMTP server; when # a non-empty value is specified, this overrides the obsolete parameters # smtpd_use_tls and smtpd_enforce_tls. # .IP "\fBtls_random_source (see 'postconf -d' output)\fR" # The external entropy source for the in-memory \fBtlsmgr\fR(8) pseudo # random number generator (PRNG) pool. # SEE ALSO # master(8) Postfix master program # postfix(1) Postfix administrative interface # README FILES # .ad # .fi # Use "\fBpostconf readme_directory\fR"or # "\fBpostconf html_directory\fR" to locate this information. # .na # .nf # TLS_README, Postfix TLS configuration and operation # LICENSE # .ad # .fi # The Secure Mailer license must be distributed with this software. # HISTORY # The "\fBpostfix tls\fR" command was introduced with Postfix # version 3.1. # AUTHOR(S) # Viktor Dukhovni #--
# Overwrite SMTP client and server settings only when these are at defaults.
client_settings="
smtp_use_tls
smtp_enforce_tls
smtp_tls_enforce_peername
smtp_tls_security_level
smtp_tls_cert_file
smtp_tls_dcert_file
smtp_tls_eccert_file "
java.lang.NullPointerException # Can't do much without these in place.
java.lang.NullPointerException
cd $command_directory || { # Let's hope there's a "postlog" somewhere else on the PATH
FATAL="postlog -p fatal -t $MAIL_LOGTAG/postfix-tls-script"
msg="no Postfix command directory '${command_directory}'"
$FATAL "$msg" || { echo "$msg" >&2; sleep 1; } exit1
}
check_getopt() {
OPTIND=1
a=
b=
c=
set -- -a 1 -b 2 -c -- -pos while getopts :a:b:c o do case $o in
a) a="${OPTARG}";;
b) b="${OPTARG}";;
c) c=3;;
*) return1;;
esac
done
shift `expr ${OPTIND} - 1` if [ "${a}" != "1" -o "${b}" != 2 -o "${c}" != 3 \
-o "${OPTIND}" -ne 7 -o "$1" != "-pos" ]; then return1
fi
}
check_getopt || {
$FATAL "/bin/sh does not implement a compatible 'getopts' built-in" exit1
}
# ----- BEGIN OpenSSL-specific -----
# No need to set the location of the OpenSSL command in each Postfix instance, # the value from the default instance is used for all instances.
java.lang.NullPointerException
default_config_directory=`$postconf -dh config_directory`
openssl=`$postconf -c $default_config_directory -xh openssl_path` "$openssl" version >/dev/null 2>&1 || {
$FATAL "No working openssl(1) command found with 'openssl_path = $openssl'" exit1
}
# ----- END OpenSSL-specific -----
test -n "$config_directory" -a -d "$config_directory" || {
$FATAL no Postfix configuration directory $config_directory! exit1
}
# Do we support TLS andif so which algorithms?
java.lang.NullPointerException
$postconf -T compile-version | grep . >/dev/null || {
mail_version=`$postconf -dh mail_version`
$FATAL "Postfix $mail_version is not compiled with TLS support" exit1
}
rsa=
ecdsa= for _algo in `$postconf -T public-key-algorithms | grep -E '^(rsa|ecdsa)$'` do
eval $_algo=$_algo
done
# ----- BEGIN OpenSSL-specific -----
if [ -n "${ecdsa}" ]; then
$openssl ecparam -name secp256r1 >/dev/null 2>&1 || {
cat <<-EOM | $WARN
Postfix supports ECDSA, but the $openssl command does not. Consider
setting the openssl_path parameter to a more capable version of the
command-line utility than $openssl (with PATH=$PATH).
EOM
ecdsa=
}
fi if [ -n "${rsa}" ]; then
DEFALG=rsa
elif [ -n "${ecdsa}" ]; then
DEFALG=ecdsa else
mail_version=`$postconf -dh mail_version`
$FATAL "Postfix $mail_version does not support either RSA or ECDSA" exit1
fi
# Make sure stdin is open when testing if [ -r /dev/stdin ] < /dev/null; then
stdin=/dev/stdin
elif [ -r /dev/fd/0 ] </dev/null; then
stdin=/dev/fd/0 else
$FATAL No /dev/fd/0or /dev/stdin found exit1
fi
# We require SHA2-256 support from openssl(1)
java.lang.NullPointerException
null256=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
tmp=`hex_sha256 </dev/null 2>/dev/null` if [ "${tmp}" != "${null256}" ]; then
cat <<EOF >&2
Your $openssl does not support the SHA2-256 digest algorithm. To enable 'postfix tls', install an OpenSSL that does. Install its openssl(1) command
at /usr/local/bin/openssl or other suitable location, and set the 'openssl_path' parameter in $default_config_directory/main.cf accordingly.
EOF
$FATAL "No 'postfix tls' support when openssl(1) is obsolete" exit1
fi
read_key() {
[ -n "$1" -a -f "$1" ] || return1
# Old OpenSSL versions return success even for unsupported sub-commands! # So we inspect the output instead. Don't prompt if the key is password # protected.
java.lang.NullPointerException while read cmd key_algo key_param cert_param; do
$openssl $cmd -passin "pass:umask 077" -in "$1" |
grep . && return0
done 2>/dev/null <<-EOF
rsa rsa smtpd_tls_key_file smtpd_tls_cert_file
ec ecdsa smtpd_tls_eckey_file smtpd_tls_eccert_file
EOF return1
}
pubkey_dgst() {
[ -n "$1" -a -f "$1" ] || return1
# Old OpenSSL versions return success even for unsupported sub-commands! # So we inspect the output instead.
java.lang.NullPointerException for cmd in ec rsa; do
$openssl $cmd -passin "pass:umask 077" -in "$1" -pubout |
$openssl $cmd -pubin -outform DER |
hex_sha256 | grep -E -v "${null256}" && return0
done 2>/dev/null return1
}
# Old OpenSSL versions return success even for unsupported sub-commands! # So we inspect the output instead.
java.lang.NullPointerException for cmd in ec rsa; do
$openssl x509 -pubkey -noout -in "$1" |
$openssl $cmd -pubin -outform DER |
hex_sha256 | grep -E -v "${null256}" && return0
done 2>/dev/null return1
}
umask 077
read_key "${_fold}" > "${_fnew}"# sets key_algo of current key
_ret=$?
umask "${_umask}"
if [ "${_ret}" -ne 0 ]; then
$FATAL "Error copying private key from '${_fold}' to '${_fnew}'" return1
fi if [ "${key_algo}" != "${_algo}" ]; then
$FATAL "Key algorithm '$key_algo' of '${_fold}' is not '${_algo}'" return1
fi # XXX: We'd need C-code in postconf to portably check for compatible "bits"
}
info_enable_client() {
cat <<-EOM
*** Non-default SMTP client TLS settings detected, no changes made. For opportunistic TLS in the Postfix SMTP client, the below settings
are typical:
smtp_tls_security_level = may
smtp_tls_loglevel = 1
EOM if get_cache_db_type dbtype
then
echo " smtp_tls_session_cache_database = ${dbtype}:\${data_directory}/smtp_scache"
fi
}
info_client_deployed() {
cat <<-EOM
Enabled opportunistic TLS in the Postfix SMTP client.
Run the command: # postfix reload if you want the new settings to take effect immediately.
EOM
}
info_enable_server() {
cat <<-EOM
*** Non-default SMTP server TLS settings detected, no changes made. For opportunistic TLS in the Postfix SMTP server, the below settings
are typical:
smtpd_tls_security_level = may
smtpd_tls_loglevel = 1
You can use "postfix tls new-server-cert" to create a new certificate. Or, "postfix tls new-server-key" to also force a newprivate key. If you publish DANE TLSA records, see:
https://tools.ietf.org/html/rfc7671#section-8
https://tools.ietf.org/html/rfc7671#section-5.1
https://tools.ietf.org/html/rfc7671#section-5.2
https://community.letsencrypt.org/t/please-avoid-3-0-1-and-3-0-2-dane-tlsa-records-with-le-certificates/7022
EOM
}
# args: certfile keyfile deploy
info_server_deployed() { if [ "$3" = "enable" ]; then
echo "Enabled opportunistic TLS in the Postfix SMTP server"
fi
cat <<-EOM New TLS private key and certificate deployed.
Run the command: # postfix reload if you want the new settings to take effect immediately.
EOM
}
# args: certfile keyfile deploy
info_csr() {
cat <<-EOM
To generate a CSR run: # postfix tls output-server-csr -k $2 [<hostname> ...]
EOM if [ -z "$3" ]; then
echo "Save the signed certificate chain in $1, and deploy as above." else
echo "Save the signed certificate chain in $1."
fi
}
# args: certfile keyfile deploy
info_tlsa() { # If already deployed, info for how to show all the deployed keys. # Otherwise, just the new keys, so that TLSA records can be updated # first. if [ -n "$3" ]; then shift $#; fi
cat <<-EOM
To generate TLSA records run: # postfix tls output-server-tlsa [-h <hostname>] $2
EOM
}
# args: certfile keyfile deploy
info_dane_dns() { # If already deployed, too late to wait, otherwise advise updating TLSA # RRs before deployment. if [ -n "$3" ]; then
cat <<-EOM
(If you have DANE TLSA RRs, update them as soon as possible to match
the newly deployed keys).
EOM else
cat <<-EOM
(deploy after updating the DNS and waiting for stale RRs to expire).
EOM
fi
}
set_fqdn() { if [ -n "$1" ]; then fqdn=$1; return0; fi
fqdn=`$postconf -xh myhostname` || return1 case $fqdn in /*) fqdn=`cat "${fqdn}"` || return 1;; esac }
if[-r"${keyfile}"];then $FATAL"Newprivatekeyfilealreadyexists:${keyfile}" return1 fi if[-r"${certfile}"];then $FATAL"Newcertificatefilealreadyexists:${certfile}" return1 fi
if[-n"$1"];then copy_key"${_algo}""${_bits}""$1""${keyfile}"&&return0 else create_key"${_algo}""${_bits}""${keyfile}"&&return0 fi rm-f"${keyfile}" return1 }
init_random_source(){ tls_random_source=$1
if[-z"${tls_random_source}"];then tls_random_source=`$postconf-xhtls_random_source` fi if[-n"${tls_random_source}"];then return0 fi if[-r/dev/urandom] then tls_random_source=dev:/dev/urandom else $FATALnodefaultTLSrandomsourcedefinedandno/dev/urandom return1 fi }
#Don'tbetoocleverbyhalf. all_default(){ forvarin"$@" do val=`$postconf-nh"${var}"` if[-n"$val"];thenreturn1;fi done return0 }
#Selectread-writedatabasetypeforTLSsessioncaches. # get_cache_db_type(){ var=$1;shift prio=0 ret=1 for_dbtypein`$postconf-m` do _prio=0 case$_dbtypein lmdb)_prio=2;; btree)_prio=1;; esac if["$_prio"-gt"$prio"] then eval"$var=\$_dbtype" prio=$_prio ret=0 fi done return$ret }
ifall_default${server_settings} then #algobitskeyfiledeploy[hostnames...] new_server_cert"${algo}""${bits}""""enable""$@"||return1 else info_enable_server|$INFO fi }
output_server_tlsa(){ hostname=$1 check_key"$2"||return1 data=`pubkey_dgst"$2"`||return1 if[-z"$data"] then $FATALerrorcomputingSHA2-256SPKIdigestof"$key" return1 fi echo"_25._tcp.$hostname.INTLSA311$data" }
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.