From: Michael Tremer <michael.tremer@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Vulnerabilities in screen 5.0.0
Date: Tue, 13 May 2025 15:45:31 +0100 [thread overview]
Message-ID: <87D50B7A-B3B1-423D-A325-19FD21FFBF88@ipfire.org> (raw)
Hello everyone,
While I am handing our tasks on the list, would anyone be up for applying a couple of security patches to screen?
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.
Best,
-Michael
next reply other threads:[~2025-05-13 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 14:45 Michael Tremer [this message]
2025-05-13 15:51 ` Adolf Belka
2025-05-13 15:54 ` Michael Tremer
2025-05-13 16:25 ` Adolf Belka
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=87D50B7A-B3B1-423D-A325-19FD21FFBF88@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.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