From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/screen: security bump to version 4.9.1
Date: Thu, 24 Aug 2023 22:38:30 +0200 [thread overview]
Message-ID: <20230824223830.44b9f4a2@windsurf> (raw)
In-Reply-To: <20230822194922.71368-1-ju.o@free.fr>
On Tue, 22 Aug 2023 21:49:21 +0200
Julien Olivain <ju.o@free.fr> wrote:
> See release announce:
> https://lists.gnu.org/archive/html/screen-users/2023-08/msg00000.html
>
> Fixes:
> CVE-2023-24626: https://www.cve.org/CVERecord?id=CVE-2023-24626
>
> Note: Buildroot installs screen as setuid, so the described scenario
> in CVE applies.
>
> This commit also rebases all patches on this release. Patch were
> regenerated with 'git format-patch -N', so patch file name changed in
> this process. The file .checkpackageignore is also updated accordingly.
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Patch series tested on branch master at commit 6d8deb4 with commands:
Applied to master, thanks. It would be nice to upstream those 5 patches
we have against screen :)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-24 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 19:49 [Buildroot] [PATCH 1/2] package/screen: security bump to version 4.9.1 Julien Olivain
2023-08-22 21:41 ` Thomas Petazzoni via buildroot
2023-08-23 19:12 ` Julien Olivain
2023-08-23 21:04 ` Thomas Petazzoni via buildroot
2023-08-24 19:28 ` Julien Olivain
2023-08-24 20:38 ` Thomas Petazzoni via buildroot [this message]
2023-09-13 16:00 ` 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=20230824223830.44b9f4a2@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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