Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] systemd: add upstream security fix
Date: Tue, 06 Jun 2017 13:36:41 +0200	[thread overview]
Message-ID: <87efuxe4ae.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170605092733.bpy3fvqazetakp4q@tarshish> (Baruch Siach's message of "Mon, 5 Jun 2017 12:27:33 +0300")

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > Hi Thomas,
 > On Mon, Jun 05, 2017 at 11:18:29AM +0200, Thomas Petazzoni wrote:
 >> On Sun,  4 Jun 2017 21:24:34 +0300, Baruch Siach wrote:
 >> > Fixes CVE-2017-9217: remote DoS (daemon crash) via a crafted DNS response with
 >> > an empty question section.
 >> > 
 >> > Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
 >> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
 >> > ---
 >> >  package/systemd/systemd.hash | 1 +
 >> >  package/systemd/systemd.mk   | 3 +++
 >> >  2 files changed, 4 insertions(+)
 >> 
 >> Applied to master, thanks. Peter: I guess this should go to the LTS
 >> branch. Baruch, can you confirm it applies to the systemd version we
 >> have in the LTS branch?

 > Cherry-pick of systemd commit a924f43f30f9c applies cleanly to systemd v232 
 > that we have in the LTS branch. I didn't build/test though.

Thanks, committed to 2017.05.x and 2017.02.x after doing a build test.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2017-06-06 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 18:24 [Buildroot] [PATCH] systemd: add upstream security fix Baruch Siach
2017-06-05  9:18 ` Thomas Petazzoni
2017-06-05  9:27   ` Baruch Siach
2017-06-06 11:36     ` 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=87efuxe4ae.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