From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 144 (testing) report
Date: Fri, 24 Apr 2020 11:40:13 +0100
Message-ID: <D6D1912E-AEB1-4D03-A33D-48C02AD71E8F@ipfire.org>
In-Reply-To: <5ea2a31f-113c-ce0c-1f4e-52dda7aa8faa@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6782161877319640816=="
List-Id: <development.lists.ipfire.org>

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

*thumbs up*

The aarch64 build unfortunately failed over night, so we might be a little bi=
t behind schedule, but hope to release as soon as possible.

Best,
-Michael

> On 24 Apr 2020, at 11:37, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>=20
> Hello *,
>=20
> upcoming Core Update 144 (testing, see: https://blog.ipfire.org/post/ipfire=
-2-25-core-update-144-is-available-for-testing)
> is running here for about 24 hours without any unexpected behaviour so far.
>=20
> Tested IPFire functionalities in detail:
> - IPsec (N2N connections only)
> - Squid (authentication enabled, using an upstream proxy)
> - OpenVPN (RW connections only)
> - IPS/Suricata (with Emerging Threats ruleset enabled)
> - Guardian
> - Quality of Service
> - DNS (with DNS over TLS and strict QNAME minimisation)
> - Tor (relay mode)
>=20
> Not least because of the criticality of the security gaps closed therein,
> I look forward to the release of Core Update 144.
>=20
> Thanks, and best regards,
> Peter M=C3=BCller
>=20


--===============6782161877319640816==--