From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernhard Bitsch <bbitsch@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Last call for Core Update 167 (was: Re: Core Updates 166 and 167)
Date: Mon, 04 Apr 2022 11:21:15 +0200
Message-ID: <66d22a30-36aa-eb54-cff2-6191529fb194@ipfire.org>
In-Reply-To: <3F5CD609-B175-4713-A3B0-4FC6968C9358@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2097862582183034576=="
List-Id: <development.lists.ipfire.org>

--===============2097862582183034576==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I think we should include the solution for bug #12838, if possible.
It isn't an urgent repair, but reinstalls the graphical presentation of=20
the hostile hits. This can be helpful for a first impression about these=20
fw hits.

Just another idea. Seeing many CTINVALID messages, it would be nice to=20
show them in the fwhits graph also.

Regards,
Bernhard

Am 02.04.2022 um 13:00 schrieb Michael Tremer:
> Hello Peter,
>=20
>> On 2 Apr 2022, at 08:42, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>>
>> 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 anothe=
r one?],
>> zlib [again], OpenSSH, and so on) which I think should be available to our
>> userbase as soon as possible.
>=20
> I don=E2=80=99t have anything left. Please await the conference call on Mon=
day for a final decision.
>=20
>> 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 8a4780de645a5b3ab42054eaf022=
c57d6849ae9a).
>=20
> Please consult with Arne on this. There are lots of small details that need=
 to be considered.
>=20
> And I am sure he has a branch with an updated kernel somewhere already.
>=20
> However, I really would like a new kernel in this release, even if that wil=
l take us a few days longer.
>=20
>> 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
>=20
> I will leave this for Stefan.
>=20
>> - https://patchwork.ipfire.org/project/ipfire/list/?series=3D2698
>=20
> I was awaiting some response from Anthony. I am not sure whether we can tak=
e silence as approval but since he has approved the previous version of the p=
atchset which has just been extended, I am sure this is okay to merge.
>=20
>> - https://patchwork.ipfire.org/project/ipfire/patch/66e4978d-6ba4-6c14-329=
c-6f7ae99ed4b2(a)ipfire.org/
>=20
> This is something for Arne.
>=20
>> 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
>=20
> -Michael

--===============2097862582183034576==--