AdGuard Home - Package Updates

nebulon

[1.10.8]

Update AdGuard Home to 0.108.0-b.55
Full changelog
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in Go 1.22.3.
Support for comments in the ipset file (#5345).
Private rDNS resolution now also affects SOA and NS requests (#6882).
Rewrite rules mechanics was changed due to improve resolving in safe search.
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.
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 not starting.
Ignoring query log for clients with ClientID set (#5812).
Subdomains of in-addr.arpa and ip6.arpa containing 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).

girish

[1.10.9]

girish

[1.10.10]

Update AdGuard Home to 0.108.0-b.57
Full changelog
Security: Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in Go 1.22.5.
The ability to disable logging using the new log.enabled configuration property (#7079).
Frontend rewritten in TypeScript.

Package Updates

[1.10.11]

Update AdGuard Home to 0.108.0-b.58
Full changelog
We thank @itz-d0dgy for reporting this vulnerability, designated CVE-2024-36814, to us.
Additionally, AdGuard Home will now try to change the permissions of its files and directories to more restrictive ones to prevent similar vulnerabilities as well as limit the access to the configuration.
We thank @go-compile for reporting this vulnerability, designated CVE-2024-36586, to us.
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.23.2.
Support for 64-bit RISC-V architecture (#5704).
Ecosia search engine is now supported in safe search (#5009).

Package Updates

[1.10.12]

Update AdGuard Home to 0.108.0-b.59
Full changelog
AdGuard Home now properly sets permissions to its files and directories on Windows
Improved filtering performance (#6818).
Repetitive statistics log messages (#7338).
Custom client cache (#7250).
Missing runtime clients with information from the system hosts file on first AdGuard Home start (#7315).

Package Updates

[1.10.13]

Package Updates

[1.10.14]

Update AdGuardHome to 0.108.0-b.61
Full Changelog
The permission check and migration on Windows has been fixed to use the Windows security model more accurately (#7400).
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.23.4][go-1.23.4].
The --no-permcheck command-line option to disable checking and migration of permissions for the security-sensitive files and directories, which caused issues on Windows (#7400).
Goroutine leak during the upstream DNS server test (#7357).
Goroutine leak during configuration update resulting in increased response time (#6818).

Package Updates

[1.10.15]

Update AdGuardHome to 0.108.0-b.62
Full Changelog
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.23.5][go-1.23.5].
The new HTTP API POST /clients/search that finds clients by their IP addresses, CIDRs, MAC addresses, or ClientIDs. See openapi/openapi.yaml for the full description.
The GET /clients/find HTTP API is deprecated. Use the new POST /clients/search API.
Request count link in the clients table (#7513).
The formatting of large numbers on the dashboard (#7329).

Package Updates

[1.10.16]

Update AdGuardHome to 0.108.0-b.63
Full Changelog
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.23.6][go-1.23.6].
The ability to specify the upstream timeout in the Web UI.
The Fastest IP address upstream mode now collects statistics for the all upstream DNS servers.
The hostnames of DHCP clients not being shown in the Top clients table on the dashboard (#7627).
The formatting of large numbers in the upstream table and query log (#7590).

Package Updates

[1.11.0]

Package Updates

[1.12.0]

Update AdGuardHome to 0.108.0-b.64
Full Changelog
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.24.1][go-1.24.1].
Invalid ICMPv6 Router Advertisement messages (#7547).
Disabled button for autofilled login form.
Formatting of elapsed times less than one millisecond.
Changes to global upstream DNS settings not applying to custom client upstream configurations.
The formatting of large numbers in the clients tables on the Client settings page (#7583).

Package Updates

[1.13.0]

Package Updates

[1.13.1]

Update AdGuardHome to 0.108.0-b.65
Full Changelog
The ability to check filtering rules for host names using an optional query type and optional ClientID or client IP address (#4036).
Optional client and qtype URL query parameters to the GET /control/check_host HTTP API.
Rules with the client modifier not working (#7708).
The search form not working in the query log (#7704).
Clearing the DNS cache on the DNS settings page now includes both global cache and custom client cache.

Package Updates

[1.13.2]

Update AdGuardHome to 0.108.0-b.66
Full Changelog
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.24.2][go-1.24.2].
Node 20 support, Node 22 will be required in future releases.
Filtering for DHCP clients (#7734).
Validation process for the HTTPS port on the Encryption Settings page.
Node 18 support.

Package Updates

[1.13.3]

Update AdGuardHome to 0.108.0-b.67
Full Changelog
Any simultaneous requests that are considered duplicates will now only result in a single request to upstreams, reducing the chance of a cache poisoning attack succeeding. This is controlled by the new configuration object pending_requests, which has a single enabled property, set to true by default.
Incorrect label on login page (#7729).

Package Updates

[1.14.0]

Switch to stable version 0.107.61 . The unstable verison contains experimental features which are breaking TLS .

Package Updates

[1.14.1]

Update AdGuardHome to 0.107.62
Full Changelog
Clients with CIDR identifiers showing zero requests on the Settings Client settings page ([#2945]).
Command line option --update when the dns.serve_plain_dns configuration property was disabled ([#7801]).
DNS cache not working for custom upstream configurations.
Validation process for the DNS-over-TLS, DNS-over-QUIC, and HTTPS ports on the Encryption Settings page.
Searching for persistent clients using an exact match for CIDR in the POST /clients/search HTTP API.

Cloudron Forum