postfix-3.5.3

diff --git a/postfix/HISTORY b/postfix/HISTORY
index 5b806f7f98bd03aab81f43d956706f493ba4c7f2..eec2fa67c242856158b4388ef84b23babec3cfc1 100644 (file)
--- a/postfix/HISTORY
+++ b/postfix/HISTORY
@@ -24737,3 +24737,19 @@ Apologies for any names omitted.
        session may cause a false 'lost connection' error for a
        concurrent TLS session in the same tlsproxy process. File:
        tlsproxy/tlsproxy.c.
+
+20200530
+
+       Bugfix (introduced: Postfix 3.1): "postfix tls deploy-server-cert"
+       did not handle a missing optional argument. File:
+       conf/postfix-tls-script.
+
+20200610
+
+       Bugfix (introduced: Postfix 3.4): in the Postfix SMTP server,
+       the SNI callback reported an error when it was called a
+       second time. This happened after the server-side TLS engine
+       sent a TLSv1.3 HelloRetryRequest (HRR) to a remote SMTP
+       client. Reported by Ján Máté, fixed by Viktor Dukhovni.
+       File: tls/tls_misc.c.
+

diff --git a/postfix/conf/postfix-tls-script b/postfix/conf/postfix-tls-script
index 2c3430a1ade647d9a0151a46f9ccb794108ae301..1a364b7fc306df0e1911b927728721ed9b868023 100644 (file)
--- a/postfix/conf/postfix-tls-script
+++ b/postfix/conf/postfix-tls-script
@@ -777,7 +777,7 @@ get_cache_db_type() {
 deploy_server_cert() {
     certfile=$1; shift
     keyfile=$1; shift
-    deploy=$1; shift
+    case $# in 0) deploy=;; *) deploy=$1; shift;; esac
 
     # Sets key_algo, key_param and cert_param
     check_key "$keyfile" || return 1

diff --git a/postfix/src/global/mail_version.h b/postfix/src/global/mail_version.h
index da996319fc0f752e6cb7d0bcad64459017571414..2e598484eaa8ce389febee90d549037470eeaf24 100644 (file)
--- a/postfix/src/global/mail_version.h
+++ b/postfix/src/global/mail_version.h
@@ -20,8 +20,8 @@
   * Patches change both the patchlevel and the release date. Snapshots have no
   * patchlevel; they change the release date only.
   */
-#define MAIL_RELEASE_DATE      "20200516"
-#define MAIL_VERSION_NUMBER    "3.5.2"
+#define MAIL_RELEASE_DATE      "20200614"
+#define MAIL_VERSION_NUMBER    "3.5.3"
 
 #ifdef SNAPSHOT
 #define MAIL_VERSION_DATE      "-" MAIL_RELEASE_DATE

diff --git a/postfix/src/tls/tls_misc.c b/postfix/src/tls/tls_misc.c
index 527233dfe00a104b12144978f9652429127cb5f3..24d8be5c7827e25a9e32710fe7da2ccef5f416cb 100644 (file)
--- a/postfix/src/tls/tls_misc.c
+++ b/postfix/src/tls/tls_misc.c
@@ -686,6 +686,27 @@ static int server_sni_callback(SSL *ssl, int *alert, void *arg)
                 TLScontext->namaddr, sni);
        return SSL_TLSEXT_ERR_NOACK;
     }
+
+    /*
+     * With TLS 1.3, when the client's proposed key share is not supported by
+     * the server, the server may issue a HelloRetryRequest (HRR), and the
+     * client will then retry with a new key share on a curve supported by
+     * the server.  This results in the SNI callback running twice for the
+     * same connection.
+     * 
+     * When that happens, The client MUST send the essentially the same hello
+     * message, including the SNI name, and since we've already loaded our
+     * certificate chain, we don't need to do it again!  Therefore, if we've
+     * already recorded the peer SNI name, just check that it has not
+     * changed, and return success.
+     */
+    if (TLScontext->peer_sni) {
+       if (strcmp(sni, TLScontext->peer_sni) == 0)
+           return SSL_TLSEXT_ERR_OK;
+       msg_warn("TLS SNI changed from %s initially %s, %s after hello retry",
+                TLScontext->namaddr, TLScontext->peer_sni, sni);
+       return SSL_TLSEXT_ERR_NOACK;
+    }
     do {
        /* Don't silently skip maps opened with the wrong flags. */
        pem = maps_file_find(tls_server_sni_maps, cp, 0);