From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: CU178 kernel fixes Testing
Date: Mon, 14 Aug 2023 16:42:40 +0100
Message-ID: <3E6FBC45-5948-40DC-AE39-C92CBA729BBB@ipfire.org>
In-Reply-To: <D30F7F36-7A1D-42B6-AA52-D79B91B3DF16@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3164816277518669303=="
List-Id: <development.lists.ipfire.org>

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

Hello,

I already bumped these again and copied them manually into the stable branch.

Users should now see those updates.

But I wasn=E2=80=99t aware of nping=E2=80=A6 I only did these:

  https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D80ff3f08c49fb=
f0580392a9afda43d99e50d43ba

-Michael

> On 14 Aug 2023, at 15:19, jon <jon.murphy(a)ipfire.org> wrote:
>=20
> What about the rebuilds like nmap, monit, nping, etc.??
>=20
> Jon Murphy
> jon.murphy(a)ipfire.org
>=20
>=20
>=20
>> On Aug 14, 2023, at 9:03 AM, Michael Tremer <michael.tremer(a)ipfire.org> =
wrote:
>>=20
>> Hello Adolf,
>>=20
>>> On 14 Aug 2023, at 12:26, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>=20
>>> Hi All,
>>>=20
>>>=20
>>> I didn't see any further notification about the kernel fixes in CU178 bei=
ng available to test but looking in the Changelog in the nightlies it seemed =
that the fixes were available in the CU178 version in master.
>>=20
>> Sorry for the confusion. Arne and I made a quick plan how to move forward =
with all those large security issues over the phone.
>>=20
>> Since I was traveling last week I didn=E2=80=99t have a chance to test the=
 update (so that at least a second pair of eyeballs has confirmed that we don=
=E2=80=99t break things really) before the announcement went out. This mornin=
g, I installed the update and pretty much immediately pressed the button for =
the announcement.
>>=20
>>> So I have tested it on 2 vm systems that I have.
>>>=20
>>> After update the systems were on 178 Development Build master/41e33931. D=
uring the reboot on both systems no issues were found and no red warning mess=
ages.
>>=20
>> Very good!
>>=20
>> We decided to push all those changes straight to the master branch so that=
 we gain more testers quickly and moved c178 to 179 and left that in next. In=
 order to be able to release the update as quickly as possible, we didn=E2=80=
=99t back port anything else from next into master as we couldn=E2=80=99t fin=
d anything that is *really* urgent.
>>=20
>>> OpenVPN RW and N2N both worked as normal after the update.
>>>=20
>>> Ran for a couple of hours and did a range of web activities.
>>>=20
>>> Everything worked as expected and all graphs reviewed showed data as norm=
ally expected.
>>>=20
>>>=20
>>> No problems found.
>>=20
>> That is the stuff I want to hear :)
>>=20
>> Unless someone reports any new regressions, I would like to release this u=
pdate maybe on Wednesday or Thursday.
>>=20
>> Best,
>> -Michael
>>=20
>>>=20
>>>=20
>>> Regards,
>>>=20
>>> Adolf.
>>>=20
>>>=20
>>=20
>=20


--===============3164816277518669303==--