From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 144 (testing) report
Date: Fri, 24 Apr 2020 12:37:13 +0200
Message-ID: <5ea2a31f-113c-ce0c-1f4e-52dda7aa8faa@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7514250226176213934=="
List-Id: <development.lists.ipfire.org>

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

Hello *,

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.

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)

Not least because of the criticality of the security gaps closed therein,
I look forward to the release of Core Update 144.

Thanks, and best regards,
Peter M=C3=BCller


--===============7514250226176213934==--