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 next 2/2] bash: bump version to 4.4
Date: Tue, 29 Nov 2016 13:40:29 +0100	[thread overview]
Message-ID: <20161129134029.25a9a847@free-electrons.com> (raw)
In-Reply-To: <20161129122404.59676-2-Vincent.Riera@imgtec.com>

Hello,

On Tue, 29 Nov 2016 12:24:04 +0000, Vicente Olivert Riera wrote:
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> Notes to maintainer
>  - This new version contains a small security fix. From
>    http://tiswww.case.edu/php/chet/bash/NEWS:
> 
>    "Shells running as root no longer inherit PS4 from the environment,
>    closing a security hole involving PS4 expansion performing command
>    substitution."
> 
>    However, taking into account that bash is a critical package and the
>    2016.11 release is very close I've marked this patch as "next".

"is a critical package" or "is *NOT* a critical package" ? If it's a
critical package like you suggest, then perhaps we want it in master
anyway ?

Thanks,

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

  reply	other threads:[~2016-11-29 12:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 12:24 [Buildroot] [PATCH next 1/2] readline: bump version to 7.0 Vicente Olivert Riera
2016-11-29 12:24 ` [Buildroot] [PATCH next 2/2] bash: bump version to 4.4 Vicente Olivert Riera
2016-11-29 12:40   ` Thomas Petazzoni [this message]
2016-11-29 12:59     ` Vicente Olivert Riera
2016-11-30 11:02   ` Peter Korsgaard
2016-11-29 12:37 ` [Buildroot] [PATCH next 1/2] readline: bump version to 7.0 Thomas Petazzoni
2016-11-29 12:56   ` Vicente Olivert Riera
2016-11-29 14:23     ` Vicente Olivert Riera
2016-11-30 11:01 ` Peter Korsgaard

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=20161129134029.25a9a847@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