All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/dovecot: security bump to version 2.3.4.1
Date: Mon, 18 Feb 2019 17:37:50 +0100	[thread overview]
Message-ID: <87pnrp9hnl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190205165710.11918-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 5 Feb 2019 17:57:10 +0100")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes the following security issues:
 >  * CVE-2019-3814: If imap/pop3/managesieve/submission client has
 >    trusted certificate with missing username field
 >    (ssl_cert_username_field), under some configurations Dovecot
 >    mistakenly trusts the username provided via authentication instead
 >    of failing.

 >  * ssl_cert_username_field setting was ignored with external SMTP AUTH,
 >    because none of the MTAs (Postfix, Exim) currently send the
 >    cert_username field. This may have allowed users with trusted
 >    certificate to specify any username in the authentication. This bug
 >    didn't affect Dovecot's Submission service.

 > For more details, see the announcement:
 > https://www.dovecot.org/list/dovecot-news/2019-February/000394.html

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2018.11.x, thanks.

For 2018.02.x I will instead bump to 2.2.36.1, which contains the same
fixes.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2019-02-18 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 16:57 [Buildroot] [PATCH] package/dovecot: security bump to version 2.3.4.1 Peter Korsgaard
2019-02-05 19:27 ` Peter Korsgaard
2019-02-18 16:37 ` Peter Korsgaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnrp9hnl.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.