AdGuard Home v0.107.22

Update 16. Dez. 2022

Ein Fehler eines Pop-ups bei der Übernahme der Einstellungen wurde behoben.

Changelog 0.107.21

Changed

• The URLs of the default filters for new installations are synchronized to those introduced in v0.107.20 (#5238).
• NOTE: Some users may need to re-add the lists from the vetted filter lists to update the URLs. Custom filters added by users themselves do not require re-adding.

Fixed

• Errors popping up during updates of settings, which could sometimes cause the server to stop responding (#5251).

Security

Go version has been updated to prevent the possibility of exploiting the CVE-2022-41717 and CVE-2022-41720 Go vulnerabilities fixed in Go 1.18.9.
Added

The ability to clear the DNS cache (#5190).
Changed

DHCP server initialization errors are now logged at debug level if the server itself disabled (#4944).
Fixed

Wrong validation error messages on the DHCP configuration page (#5208).
Slow upstream checks making the API unresponsive (#5193).
The TLS initialization errors preventing AdGuard Home from starting (#5189). Instead, AdGuard Home disables encryption and shows an error message on the encryption settings page in the UI, which was the intended previous behavior. URLs of some vetted blocklists.

Bug Fix:

Crash on some systems when domains from system hosts files are processed (#5089)

Added

The warning message when adding a certificate having no IP addresses (#4898). Several new blockable services (#3972). Those will now be more in sync with the services that are already blockable in AdGuard DNS. A new HTTP API, GET /control/blocked_services/all, that lists all available blocked services and their data, such as SVG icons (#3972). The new optional tls.override_tls_ciphers property, which allows overriding TLS ciphers used by AdGuard Home (#4925, #4990). The ability to serve DNS on link-local IPv6 addresses (#2926). The ability to put ClientIDs into DNS-over-HTTPS hostnames as opposed to URL paths (#3418). Note that AdGuard Home checks the server name only if the URL does not contain a ClientID.

Changed

DNS-over-TLS resolvers aren't returned anymore when the configured TLS certificate contains no IP addresses (#4927). Responses with SERVFAIL code are now cached for at least 30 seconds.

Deprecated

The GET /control/blocked_services/services HTTP API; use the new GET /control/blocked_services/all API instead (#3972).

Fixed

ClientIDs not working when using DNS-over-HTTPS with HTTP/3. Editing the URL of an enabled rule list also includes validation of the filter contents preventing from saving a bad one (#4916). The default value of dns.cache_size accidentally set to 0 has now been reverted to 4 MiB (#5010). Responses for which the DNSSEC validation had explicitly been omitted aren't cached now (#4942). Web UI not switching to HTTP/3 (#4986, #4993).

BTW: Bietet AdGuard grad einen 40% Halloween-Sale an.

https://adguard.com/de/license…=33256&utm_source=topline