Core Update 144 (testing) report

Core Update 144 (testing) report

[Peter Müller]

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

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üller

Re: Core Update 144 (testing) report

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

*thumbs up*

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

Best,
-Michael

> On 24 Apr 2020, at 11:37, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> 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üller
>