From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Andrej Valek <andrej.valek@siemens.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: bussybox: updating to new version
Date: Fri, 18 Aug 2017 11:12:02 -0500 [thread overview]
Message-ID: <1503072722.28682.36.camel@linux.intel.com> (raw)
In-Reply-To: <78647462-c423-bdc3-8adb-544fe8eee978@siemens.com>
On Fri, 2017-08-18 at 12:16 +0200, Andrej Valek wrote:
> Hello everyone,
>
> I would like to ask you a question about busybox upgrading.
>
> Is there any reason, why we are still using the version 1.24.1?
> I think that, the latest version 1.27.2 has a lot of fixes and it less
> vulnerable then the current.
>
feel free to send a patch with the upgrade. BTW, this is the upgrade
history of the recipe
http://recipes.yoctoproject.org/rrs/recipedetail/12601/
> I have checked a license and it has not been changed.
>
> Thank you for the explanation.
>
> Andrej
next prev parent reply other threads:[~2017-08-18 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 10:16 bussybox: updating to new version Andrej Valek
2017-08-18 16:00 ` Khem Raj
2017-08-18 16:12 ` Leonardo Sandoval [this message]
2017-09-04 11:34 ` Burton, Ross
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=1503072722.28682.36.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=andrej.valek@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
/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