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 143 (testing) report
Date: Sun, 12 Apr 2020 16:01:44 +0200
Message-ID: <57b6bd15-94d5-f25c-0b74-971cbe6cdf92@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5165516336937564100=="
List-Id: <development.lists.ipfire.org>

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

Hello *,

upcoming Core Update 143 (testing, see: https://blog.ipfire.org/post/ipfire-2=
-25-core-update-143-is-available-for-testing)
is running here since Thursday without any unexpected behaviour so far.

Since testing machine runs on x86_64, remote login via OpenSSH 8.2p1 did not =
cause any trouble
(tested with RSA public key authentication only), however, Arne patched sandb=
ox-seccomp-filter.c
so it works on i[5-6]86, too. Interesting to see that this kind of thing is n=
ecessary... :-/

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)

I look forward to the release of Core Update 143. Happy Easter!

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

--===============5165516336937564100==--