AdGuard Home v0.107.26

Changelog v0.107.25

• This is a hotfix release to prevent panics when using unencrypted DNS-over-HTTP, which affected people running AdGuard Home behind an HTTP reverse proxy.

Changelog v0.107.24 - 15.02.2023

Security

• Go version has been updated, both because Go 1.18 has reached end of life and to prevent the possibility of exploiting the Go vulnerabilities fixed in Go 1.19.6.

Added

• The ability to disable statistics by using the new statistics.enabled field. Previously it was necessary to set the statistics_interval to 0, losing the previous value (#1717, #4299).
• The ability to exclude domain names from the query log or statistics by using the new querylog.ignored or statistics.ignored fields (#1717, #4299). The UI changes are coming in the upcoming releases.

Changed

Configuration Changes

In this release, the schema version has changed from 14 to 16.

• Property statistics_interval, which in schema versions 15 and earlier used to be a part of the dns object, is now a part of the statistics object:
• The fields dns.querylog_enabled, dns.querylog_file_enabled, dns.querylog_interval, and dns.querylog_size_memory have been moved to the new querylog object.

# BEFORE:
'dns':  # …  'statistics_interval': 1

# AFTER:
'statistics':  # …  'interval': 1

To rollback this change, move the property back into the dns object and change the schema_version back to 15.

# BEFORE:
'dns':  'querylog_enabled': true  'querylog_file_enabled': true  'querylog_interval': '2160h'  'querylog_size_memory': 1000

# AFTER:
'querylog':  'enabled': true  'file_enabled': true  'interval': '2160h'  'size_memory': 1000

To rollback this change, rename and move properties back into the dns object, remove querylog object and querylog.ignored property, and change the schema_version back to 14.

Deprecated

• Go 1.19 support. Future versions will require at least Go 1.20 to build.

Fixed

• Setting the AD (Authenticated Data) flag on responses that have the DO (DNSSEC OK) flag set but not the AD flag (#5479).
• Client names resolved via reverse DNS not being updated (#4939).
• The icon for League Of Legends on the Blocked services page (#5433).

Removed

• Go 1.18 support, as it has reached end of life.

Changelog v0.107.23 - 01.02.2023

Added

• DNS64 support (#5117). The function may be enabled with new use_dns64 field under dns object in the configuration along with dns64_prefixes, the set of exclusion prefixes to filter AAAA responses. The Well-Known Prefix (64:ff9b::/96) is used if no custom prefixes are specified.

Fixed

• Filtering rules with * as the hostname not working properly (#5245).
• Various dark theme bugs (#5375).

Removed

• The “beta frontend” and the corresponding APIs. They never quite worked properly, and the future new version of AdGuard Home API will probably be different.

  Correspondingly, the configuration parameter beta_bind_port has been removed as well.

https://github.com/AdguardTeam…me/releases/tag/v0.107.23

Update 19. Jan. 2023

Die neue Version von AdGuard bringt einen experimentellen Darkmode mit. Einige Anpassungen sind noch nicht final, dennoch macht es einen soliden Eindruck. Des Weiteren gibt es Änderungen an der API sowie Fehlerbehebungen.

Changelog 0.107.22

Added

• Experimental Dark UI theme (#613).
• The new HTTP API PUT /control/profile/update, that updates current user language and UI theme. The format of request body is described in openapi/openapi.yaml.

Changed

• The HTTP API GET /control/profile now returns enhanced object with current user's name, language, and UI theme. The format of response body is described in openapi/openapi.yaml and openapi/CHANGELOG.md.

Fixed

• AdGuardHome --update freezing when another instance of AdGuard Home is running (#4223, #5191).
• The --update flag performing an update even when there is no version change.
• Failing HTTPS redirection on saving the encryption settings (#4898).
• Zeroing rules counter of erroneously edited filtering rule lists (#5290).
• Filters updating strategy, which could sometimes lead to use of broken or incompletely downloaded lists (#5258).

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