public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <D6D1912E-AEB1-4D03-A33D-48C02AD71E8F@ipfire.org> (raw)
In-Reply-To: <5ea2a31f-113c-ce0c-1f4e-52dda7aa8faa@ipfire.org>

[-- 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
> 


      reply	other threads:[~2020-04-24 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 10:37 Peter Müller
2020-04-24 10:40 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D6D1912E-AEB1-4D03-A33D-48C02AD71E8F@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox