From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Core Update 169 merge window closes by the end of this week Date: Tue, 14 Jun 2022 12:00:45 +0000 Message-ID: <74c4bc99-2abf-207f-da52-d94c80565966@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1460778411578805465==" List-Id: --===============1460778411578805465== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello development folks, as discussed yesterday (https://wiki.ipfire.org/devel/telco/2022-06-13), I wo= uld like to close the merge window for Core Update 169 by the end of this week (i.e. Sunday). Currently, the update features a toolchain update, to bring some GCC fixes to= our users. An updated kernel plugs several recently disclosed security vulnerabilities, som= e of them related to BPF. None of them is critical and/or remotely exploitable, but they levera= ge local privilege escalation, which we don't want in IPFire. :-) Lastly, an updated linux-firmw= are petting zoo brings all the shiny proprietary firmware of various vendors to our users, an= d we can only hope that they benefit from whatever changes were made in all these binary blobs. Currently, the update is pretty large (95 MBytes) already. Should any of you = have changes in the pipeline that are space-intensive, I would like to abstain from including= them in C169, and rather put them into C170. Michael's OpenVPN 2FA merge request is yet to come, and I need to update U-Bo= ot. To cut it short, please submit patches you want to have in C169 soon. It is m= y intention to provide our users with a testing Core Update as soon as possible, ideally not= waiting as long for the final release as we unfortunately had to with C168. Stay safe, and best regards, Peter M=C3=BCller --===============1460778411578805465==--