postfix-2.7.4

diff --git a/postfix/HISTORY b/postfix/HISTORY
index 980ff8d796e8a45e255dc0e9bd36ed4040b021b8..a4922c08e687beb3d3fc069e5b5a3f8d5fa843ee 100644 (file)
--- a/postfix/HISTORY
+++ b/postfix/HISTORY
@@ -15616,7 +15616,7 @@ Apologies for any names omitted.
        for the "virtual:" transport to "/etc/postfix/virtual:".
        Symptom reported by Christoph Anton Mitterer.
 
-20200102
+20100102
 
        Workaround: don't report bogus Berkeley DB close errors as
        fatal errors. All operations before close are already error
@@ -15884,3 +15884,10 @@ Apologies for any names omitted.
 
        Portability: FreeBSD closefrom() support time window.  Sahil
        Tandon.  File: util/sys_defs.h.
+
+20110414
+
+       Bugfix (introduced with Postfix SASL patch 20000314): don't
+       reuse a server SASL handle after authentication failure.
+       Problem reported by Thomas Jarosch of Intra2net AG. File:
+       smtpd/smtpd_proto.c.

diff --git a/postfix/src/global/mail_version.h b/postfix/src/global/mail_version.h
index 422598398a412f39cd5eb757417fa183b09e7efb..8e3f5d5b65c20327c13000a333721d434f5b018e 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      "20110303"
-#define MAIL_VERSION_NUMBER    "2.7.3"
+#define MAIL_RELEASE_DATE      "20110509"
+#define MAIL_VERSION_NUMBER    "2.7.4"
 
 #ifdef SNAPSHOT
 # define MAIL_VERSION_DATE     "-" MAIL_RELEASE_DATE

diff --git a/postfix/src/smtpd/smtpd_sasl_proto.c b/postfix/src/smtpd/smtpd_sasl_proto.c
index 89064feb0ceb85631a162431c6c395c1e0ada313..1633a80bec67440a9b7a4a6c6902200fc53e8b62 100644 (file)
--- a/postfix/src/smtpd/smtpd_sasl_proto.c
+++ b/postfix/src/smtpd/smtpd_sasl_proto.c
@@ -184,6 +184,27 @@ int     smtpd_sasl_auth_cmd(SMTPD_STATE *state, int argc, SMTPD_TOKEN *argv)
        return (-1);
     }
 
+    /* Don't reuse the SASL handle after authentication failure. */
+#ifndef SMTPD_FLAG_AUTH_USED
+#define SMTPD_FLAG_AUTH_USED   (1<<15)
+#endif
+#ifndef XSASL_TYPE_CYRUS 
+#define XSASL_TYPE_CYRUS       "cyrus"
+#endif
+    if (state->flags & SMTPD_FLAG_AUTH_USED) {
+       smtpd_sasl_deactivate(state);
+#ifdef USE_TLS
+       if (state->tls_context != 0)
+           smtpd_sasl_activate(state, VAR_SMTPD_SASL_TLS_OPTS,
+                               var_smtpd_sasl_tls_opts);
+       else
+#endif
+           smtpd_sasl_activate(state, VAR_SMTPD_SASL_OPTS,
+                               var_smtpd_sasl_opts);
+    } else if (strcmp(var_smtpd_sasl_type, XSASL_TYPE_CYRUS) == 0) {
+       state->flags |= SMTPD_FLAG_AUTH_USED;
+    }
+
     /*
      * All authentication failures shall be logged. The 5xx reply code from
      * the SASL authentication routine triggers tar-pit delays, which help to