Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: buildroot@busybox.net
Subject: [Buildroot] busybox update 1.29.x on LTS branch?
Date: Tue, 31 Jul 2018 13:21:58 +0200	[thread overview]
Message-ID: <20180731112158.GY21354@australia> (raw)

Hi Peter,

Busybox 1.29.x is fixing CVE issues, like https://nvd.nist.gov/vuln/detail/CVE-2018-1000517
and https://nvd.nist.gov/vuln/detail/CVE-2018-1000500, both fixed in 1.29.0.

I was wondering if you are planning on bumping busybox on the LTS branch too?

Thanks,
Thomas

             reply	other threads:[~2018-07-31 11:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 11:21 Thomas De Schampheleire [this message]
2018-08-09 21:58 ` [Buildroot] busybox update 1.29.x on LTS branch? 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=20180731112158.GY21354@australia \
    --to=thomas.de_schampheleire@nokia.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