From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= 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 Message-ID: <46cf3911-be70-05d8-eb17-55e62aa9ad11@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8473854417533079893==" List-Id: --===============8473854417533079893== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 o= ne?], 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 8a4780de645a5b3ab42054eaf022c57= d6849ae9a). 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=3D2684 - https://patchwork.ipfire.org/project/ipfire/list/?series=3D2698 - https://patchwork.ipfire.org/project/ipfire/patch/66e4978d-6ba4-6c14-329c-6= f7ae99ed4b2(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=C3=BCller --===============8473854417533079893==--