AdGuard Home v0.107.49
Fast approaching summer promises everyone its warmth, and all kinds of bugs are crawling from under the rocks and twigs to enjoy the sun 🌞. Here's a patch to make sure that they stay in the grass and nowhere near AdGuard Home.
Acknowledgements
A special thanks to our community moderation team, @AdguardTeam/community-moderators, contributor @looklose, as well as to everyone who filed and inspected issues, added translations, and helped us test this release!
Full changelog
Security
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in Go 1.22.3.
Added
- Support for comments in the ipset file (#5345).
Changed
-
Private rDNS resolution now also affects
SOAandNSrequests (#6882). -
Rewrite rules mechanics were changed due to improved resolving in safe search.
Deprecated
- Currently, AdGuard Home skips persistent clients that have duplicate fields when reading them from the configuration file. This behaviour is deprecated and will cause errors on startup in a future release.
Fixed
-
Acceptance of duplicate UIDs for persistent clients at startup. See also the section on client settings on the Wiki page.
-
Domain specifications for top-level domains not considered for requests to unqualified domains (#6744).
-
Support for link-local subnets, i.e.
fe80::/16, as client identifiers (#6312). -
Issues with QUIC and HTTP/3 upstreams on older Linux kernel versions (#6422).
-
YouTube restricted mode is not enforced by HTTPS queries on Firefox.
-
Support for link-local subnets, i.e.
fe80::/16, in the access settings (#6192). -
The ability to apply an invalid configuration for private RDNS, which led to server inoperability.
-
Ignoring query log for clients with ClientID set (#5812).
-
Subdomains of
in-addr.arpaandip6.arpacontaining zero-length prefix incorrectly considered invalid when specified for private RDNS upstream servers (#6854). -
Unspecified IP addresses aren't checked when using "Fastest IP address" mode (#6875).
