From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 154 (testing) report
Date: Mon, 01 Mar 2021 19:22:49 +0100 [thread overview]
Message-ID: <9b8079d5-aaf2-982e-8f8f-8b94ce069f5d@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
Hello *,
Core Update 154 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-154-available-for-testing)
is running here for a couple of weeks by now without any known issues so far - sorry for my tardy report.
As expected, Unbound is now reusing TCP and TLS connections, making huge improvements of resolution times for
machines using something else than UDP for querying DNS resolvers. Except for a initial delay, DoT does not
introduce any significant performance impact anymore. Upcoming Unbound version will support padding of DNS over
TLS traffic, making guessing queried FQDNs even harder to passive adversaries.
In a rather gloomy world in terms of privacy, I guess that is good news. :-)
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 community ruleset enabled)
- Guardian
- Quality of Service
- DNS (using DNS over TLS and strict QNAME minimisation)
- Dynamic DNS
- Tor (relay mode)
I look forward to the release of Core Update 154.
Thanks, and best regards,
Peter Müller
reply other threads:[~2021-03-01 18:22 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=9b8079d5-aaf2-982e-8f8f-8b94ce069f5d@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