From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 143 (testing) report
Date: Sun, 12 Apr 2020 16:01:44 +0200 [thread overview]
Message-ID: <57b6bd15-94d5-f25c-0b74-971cbe6cdf92@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
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 sandbox-seccomp-filter.c
so it works on i[5-6]86, too. Interesting to see that this kind of thing is necessary... :-/
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üller
reply other threads:[~2020-04-12 14:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=57b6bd15-94d5-f25c-0b74-971cbe6cdf92@ipfire.org \
--to=peter.mueller@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