Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dbus: security bump to version 1.8.14
Date: Tue, 6 Jan 2015 21:14:58 +0100	[thread overview]
Message-ID: <20150106211458.254bc7b8@free-electrons.com> (raw)
In-Reply-To: <1420542132-12262-1-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Tue,  6 Jan 2015 08:02:12 -0300, Gustavo Zacarias wrote:
> Fixes CVE-2014-8148 - If a system service installs unsafe security
> policy rules that allow arbitrary method calls then this prevents memory
> consumption and possible privilege escalation via
> UpdateActivationEnvironment.
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/dbus/dbus.hash | 2 +-
>  package/dbus/dbus.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-01-06 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 11:02 [Buildroot] [PATCH] dbus: security bump to version 1.8.14 Gustavo Zacarias
2015-01-06 20:14 ` Thomas Petazzoni [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=20150106211458.254bc7b8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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