public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
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	[thread overview]
Message-ID: <74c4bc99-2abf-207f-da52-d94c80565966@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

Hello development folks,

as discussed yesterday (https://wiki.ipfire.org/devel/telco/2022-06-13), I would 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, some of them related
to BPF. None of them is critical and/or remotely exploitable, but they leverage local privilege
escalation, which we don't want in IPFire. :-) Lastly, an updated linux-firmware petting zoo
brings all the shiny proprietary firmware of various vendors to our users, and 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-Boot.

To cut it short, please submit patches you want to have in C169 soon. It is my 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üller

             reply	other threads:[~2022-06-14 12:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 12:00 Peter Müller [this message]
2022-06-16 12:47 ` Matthias Fischer

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=74c4bc99-2abf-207f-da52-d94c80565966@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