Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnutls: security bump to version 3.5.10
Date: Tue, 07 Mar 2017 16:10:43 +0100	[thread overview]
Message-ID: <87zigxcebw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170306174643.33835439@free-electrons.com> (Thomas Petazzoni's message of "Mon, 6 Mar 2017 17:46:43 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Hello,
 > On Mon,  6 Mar 2017 11:55:06 -0300, Gustavo Zacarias wrote:
 >> Fixes:
 >> GNUTLS-SA-2017-3A - Addressed integer overflow resulting to invalid
 >> memory write in OpenPGP certificate parsing.
 >> GNUTLS-SA-2017-3B - Addressed crashes in OpenPGP certificate parsing,
 >> related to private key parser. No longer allow OpenPGP certificates
 >> (public keys) to contain private key sub-packets.
 >> GNUTLS-SA-2017-3C - Addressed large allocation in OpenPGP certificate
 >> parsing, that could lead in out-of-memory condition.
 >> 
 >> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
 >> ---
 >> package/gnutls/gnutls.hash | 2 +-
 >> package/gnutls/gnutls.mk   | 2 +-
 >> 2 files changed, 2 insertions(+), 2 deletions(-)

 > Applied to master, thanks. Peter: we want this one for LTS I guess.

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2017-03-07 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 14:55 [Buildroot] [PATCH] gnutls: security bump to version 3.5.10 Gustavo Zacarias
2017-03-06 16:46 ` Thomas Petazzoni
2017-03-07 15:10   ` 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=87zigxcebw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox