From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] screen: Version bump. 5.0.0 -> 5.0.1
Date: Fri, 16 May 2025 09:46:33 +0200 [thread overview]
Message-ID: <aCbtWSbH5gRpLtYU@pengutronix.de> (raw)
In-Reply-To: <20250515173851.1147261-1-christian.melki@t2data.com>
On Thu, May 15, 2025 at 07:38:51PM +0200, Christian Melki wrote:
> Security and other fixes.
> https://lists.gnu.org/archive/html/info-gnu/2025-05/msg00002.html
>
> Security fixes:
> CVE-2025-46805: do NOT send signals with root privileges
> CVE-2025-46804: avoid file existence test information leaks
> CVE-2025-46803: apply safe PTY default mode of 0620
> CVE-2025-46802: prevent temporary 0666 mode on PTYs in attacher
> CVE-2025-23395: reintroduce lf_secreopen() for logfile
>
> * Forward patchset, applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
> .../{screen-5.0.0 => screen-5.0.1}/0001-suppress_remap.patch | 0
> patches/{screen-5.0.0 => screen-5.0.1}/autogen.sh | 0
> patches/{screen-5.0.0 => screen-5.0.1}/series | 0
> rules/screen.make | 4 ++--
> 4 files changed, 2 insertions(+), 2 deletions(-)
> rename patches/{screen-5.0.0 => screen-5.0.1}/0001-suppress_remap.patch (100%)
> rename patches/{screen-5.0.0 => screen-5.0.1}/autogen.sh (100%)
> rename patches/{screen-5.0.0 => screen-5.0.1}/series (100%)
>
> diff --git a/patches/screen-5.0.0/0001-suppress_remap.patch b/patches/screen-5.0.1/0001-suppress_remap.patch
> similarity index 100%
> rename from patches/screen-5.0.0/0001-suppress_remap.patch
> rename to patches/screen-5.0.1/0001-suppress_remap.patch
> diff --git a/patches/screen-5.0.0/autogen.sh b/patches/screen-5.0.1/autogen.sh
> similarity index 100%
> rename from patches/screen-5.0.0/autogen.sh
> rename to patches/screen-5.0.1/autogen.sh
> diff --git a/patches/screen-5.0.0/series b/patches/screen-5.0.1/series
> similarity index 100%
> rename from patches/screen-5.0.0/series
> rename to patches/screen-5.0.1/series
> diff --git a/rules/screen.make b/rules/screen.make
> index 1bac9b8b8..69a65a9b8 100644
> --- a/rules/screen.make
> +++ b/rules/screen.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_SCREEN) += screen
> #
> # Paths and names
> #
> -SCREEN_VERSION := 5.0.0
> -SCREEN_MD5 := befc115989242ed4bceeff8d8bfeb4e6
> +SCREEN_VERSION := 5.0.1
> +SCREEN_MD5 := 4306c5446abd48b7899a211c4d0456b2
Hmm, I'm getting a different md5 here. Can you check what is going on here?
Michael
> SCREEN := screen-$(SCREEN_VERSION)
> SCREEN_SUFFIX := tar.gz
> SCREEN_URL := $(call ptx/mirror, GNU, screen/$(SCREEN).$(SCREEN_SUFFIX))
> --
> 2.34.1
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-05-16 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 17:38 Christian Melki
2025-05-16 7:46 ` Michael Olbrich [this message]
2025-05-16 16:25 ` Christian Melki
2025-05-16 17:55 ` Michael Olbrich
2025-05-16 22:02 ` [ptxdist] [APPLIED] " Michael Olbrich
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=aCbtWSbH5gRpLtYU@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--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