mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] busybox: Version bump. 1.35.0 -> 1.36.0
Date: Wed, 4 Jan 2023 10:10:07 +0100	[thread overview]
Message-ID: <Y7VCb1WrB2NIYAfA@lenoch> (raw)
In-Reply-To: <20230103222922.2143458-1-christian.melki@t2data.com>

Hi Christian,

On Tue, Jan 03, 2023 at 11:29:22PM +0100, Christian Melki wrote:
> After a year of low activity and questionmarks,
> we finally have a new release of busybox.
> Release changelog @ https://busybox.net/
> 
> Not that many new features, mostly fixes.
> One notable addition is seedrng.
> But it marks a new release that includes security fixes.
> 
> Plugs CVEs: CVE-2022-28391, CVE-2022-30065
> 
> * Forward the ptxdist specific patches.
> * Remove one security patch to awk that has been fixed.
> * Update busybox imported kconfig tree.
> Not that many changes, since it has been a slow year.
> New utilites: tsort, seedrng and tree.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
>  config/busybox/Config.in                      |  4 +-
>  config/busybox/coreutils/Config.in            |  7 ++-
>  config/busybox/libbb/Config.in                | 62 ++++++++++++++++---
>  config/busybox/miscutils/Config.in            | 12 ++++
>  config/busybox/networking/Config.in           |  2 +-
>  config/busybox/networking/udhcp/Config.in     |  7 ++-
>  config/busybox/shell/Config.in                |  5 ++
>  ...wk-fix-use-after-free-CVE-2022-30065.patch | 29 ---------
>  .../0200-reactivate-check-for-tty.patch       |  0
>  ...-only-pass-real-libs-to-SELINUX_LIBS.patch |  2 +-
>  ...honour-SKIP_STRIP-and-don-t-strip-if.patch |  0
>  .../{busybox-1.35.0 => busybox-1.36.0}/series |  3 +-
>  12 files changed, 89 insertions(+), 44 deletions(-)
>  delete mode 100644 patches/busybox-1.35.0/0203-awk-fix-use-after-free-CVE-2022-30065.patch
>  rename patches/{busybox-1.35.0 => busybox-1.36.0}/0200-reactivate-check-for-tty.patch (100%)
>  rename patches/{busybox-1.35.0 => busybox-1.36.0}/0201-build-system-only-pass-real-libs-to-SELINUX_LIBS.patch (94%)
>  rename patches/{busybox-1.35.0 => busybox-1.36.0}/0202-scripts-trylink-honour-SKIP_STRIP-and-don-t-strip-if.patch (100%)
>  rename patches/{busybox-1.35.0 => busybox-1.36.0}/series (74%)

It seems rules/busybox.make is ommited from the patch...

	ladis



      reply	other threads:[~2023-01-04  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 22:29 Christian Melki
2023-01-04  9:10 ` Ladislav Michl [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=Y7VCb1WrB2NIYAfA@lenoch \
    --to=oss-lists@triops.cz \
    --cc=ptxdist@pengutronix.de \
    /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