From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Last call for Core Update 167 (was: Re: Core Updates 166 and 167)
Date: Sat, 02 Apr 2022 07:42:10 +0000 [thread overview]
Message-ID: <46cf3911-be70-05d8-eb17-55e62aa9ad11@ipfire.org> (raw)
In-Reply-To: <a19176a0-e95e-b58b-aa0e-35ce80ffa056@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Hello development folks,
being responsible for upcoming Core Update 167, I would like to close this
update roughly at the beginning of next week. This is because it contains
several security-relevant updates (such as Apache, Bind [might need another one?],
zlib [again], OpenSSH, and so on) which I think should be available to our
userbase as soon as possible.
To have CVE-2022-1015 and CVE-2022-1016 covered, I will submit a patch for
an updated kernel later this day, since we have enough space to ship one as
the linux-firmware changes were reverted (see 8a4780de645a5b3ab42054eaf022c57d6849ae9a).
Looking at Patchwork, it would be great if we could clarify the status of
these patches and patch series, and whether they should go into Core Update
167 or not:
- https://patchwork.ipfire.org/project/ipfire/list/?series=2684
- https://patchwork.ipfire.org/project/ipfire/list/?series=2698
- https://patchwork.ipfire.org/project/ipfire/patch/66e4978d-6ba4-6c14-329c-6f7ae99ed4b2(a)ipfire.org/
If there are any patches sitting around in your local/private repositories
you want to have in Core Update 167, kindly post them. As always, drop me a
line in case of questions or comments.
Thanks, and best regards,
Peter Müller
next parent reply other threads:[~2022-04-02 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a19176a0-e95e-b58b-aa0e-35ce80ffa056@ipfire.org>
2022-04-02 7:42 ` Peter Müller [this message]
2022-04-02 11:00 ` Michael Tremer
2022-04-02 11:30 ` Peter Müller
2022-04-02 14:16 ` Michael Tremer
2022-04-04 9:21 ` Bernhard Bitsch
2022-04-02 14:54 ` Stefan Schantl
2022-04-11 6:21 ` Bernhard Bitsch
2022-04-11 7:49 ` Michael Tremer
2022-04-11 19:14 ` Rob Brewer
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=46cf3911-be70-05d8-eb17-55e62aa9ad11@ipfire.org \
--to=peter.mueller@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