From: Adolf Belka <adolf.belka@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Vulnerabilities in screen 5.0.0
Date: Tue, 13 May 2025 18:25:22 +0200 [thread overview]
Message-ID: <726c2765-efe1-43d8-a426-53a9ce500ac7@ipfire.org> (raw)
In-Reply-To: <CD098237-640C-4A81-B368-C9A6EC1807C3@ipfire.org>
Hi Michael,
On 13/05/2025 17:54, Michael Tremer wrote:
> Thank you!
>
>> On 13 May 2025, at 16:51, Adolf Belka <adolf.belka@ipfire.org> wrote:
>>
>> Hi Michael,
>> On 13/05/2025 16:45, Michael Tremer wrote:
>>> Hello everyone,
>>> While I am handing our tasks on the list, would anyone be up for applying a couple of security patches to screen?
>>
>> I am doing various update builds anyway so I will pick that up next.
>>
>> Regards,
>> Adolf.
>>
>>> https://www.openwall.com/lists/oss-security/2025/05/12/1
>>> The fixes are attached to the email. I don’t believe a new version has been released, yet.
I just found that version 5.0.1 has been "released" yesterday but is not yet in the source tarball download directory but it says it will come soon.
I might just wait a while to see if that comes "soon".
I have a question anyway, about the patches from that email. the filename of the 5.0.0 patch is
screen_5_0_0_patches_tar_gz.bin
I have no idea why it is showing up as a bin file, but I am not keen to download and try and open it up. Not sure how to open it anyway, depending what the .bin means anyway.
Regards,
Adolf.
>>> Best,
>>> -Michael
>>
>>
>
prev parent reply other threads:[~2025-05-13 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 14:45 Michael Tremer
2025-05-13 15:51 ` Adolf Belka
2025-05-13 15:54 ` Michael Tremer
2025-05-13 16:25 ` Adolf Belka [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=726c2765-efe1-43d8-a426-53a9ce500ac7@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@ipfire.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