Hello Peter, > On 2 Apr 2022, at 08:42, Peter Müller wrote: > > 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. I don’t have anything left. Please await the conference call on Monday for a final decision. > 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). Please consult with Arne on this. There are lots of small details that need to be considered. And I am sure he has a branch with an updated kernel somewhere already. However, I really would like a new kernel in this release, even if that will take us a few days longer. > 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 I will leave this for Stefan. > - https://patchwork.ipfire.org/project/ipfire/list/?series=2698 I was awaiting some response from Anthony. I am not sure whether we can take silence as approval but since he has approved the previous version of the patchset which has just been extended, I am sure this is okay to merge. > - https://patchwork.ipfire.org/project/ipfire/patch/66e4978d-6ba4-6c14-329c-6f7ae99ed4b2(a)ipfire.org/ This is something for Arne. > 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 -Michael