AdGuard Home - Package Updates
-
[1.1.0]
- Update AdGuard Home to 0.105.0
- Full changelog
- Client ID support for DNS-over-HTTPS, DNS-over-QUIC, and DNS-over-TLS
- Added more services to the "Blocked services" list (#2224, #2401).
- The host checking API and the query logs API can now return multiple matched rules (#2102).
- HTTP API request body size limit (#2305).
-
[1.2.1]
- Update AdGuar Home to 0.105.2
- Full changelog
- Security: Session token doesn't contain user's information anymore
- Incomplete hostnames with trailing zero-bytes handling (#2582).
- Wrong DNS-over-TLS ALPN configuration (#2681).
- Inconsistent responses for messages with EDNS0 and AD when DNS caching is enabled (#2600).
-
[1.3.0]
- Update AdGuardHome to 0.106.0
- Full changelog
- ability to set up custom upstreams to resolve PTR queries for local addresses and to disable the automatic resolving of clients' addresses
- Search by clients' names in the query log
- The ability to block user for login after configurable number of unsuccessful attempts for configurable time (#2826).
- $denyallow modifier for filters (#2923).
- Hostname uniqueness validation in the DHCP server (#2952).
- Hostname generating for DHCP clients which don't provide their own (#2723).
-
[1.3.1]
- Update AdGuardHome to 0.106.1
- Full changelog
- Local domain name handling when the DHCP server is disabled (#3028).
- Normalization of perviously-saved invalid static DHCP leases (#3027).
- Validation of IPv6 addresses with zones in system resolvers (#3022).
-
[1.4.0]
- Update AdGuard Home to 0.107.0
- Full changelog
- RFC 9000 support In DNS-over-QUIC
- DNS-over-HTTPS queries now use the real IP address of the client instead of the address of the proxy (#2799)
- Optimistic DNS cache
- Query log search now supports internationalized domains
-
[1.4.1]
- Update AdGuard Home to 0.107.2
- Full changelog
- Infinite loops when TCP connections time out (#4042).
- The validation error message for duplicated allow- and blocklists in DNS settings now shows the duplicated elements (#3975).
- ipset initialization bugs (#4027).
- Legacy DNS rewrites from a wildcard pattern to a subdomain (#4016).
- Service not being stopped before running the uninstall service action (#3868).
- Legacy DNS rewrites responding from upstream when a request other than A or AAAA is received (#4008).
- Panic on port availability check during installation (#3987).
- Incorrect application of rules from the OS's hosts files (#3998).
-
[1.4.2]
- Update AdGuard Home to 0.107.3
- Full changelog
- Support for a $dnsrewrite modifier with an empty NOERROR response (#4133).
- Wrong set of ports checked for duplicates during the initial setup (#4095).
- Incorrectly invalidated service domains (#4120).
- Poor testing of domain-specific upstream servers (#4074).
- Omitted aliases of hosts specified by another line within the OS's hosts file (#4079).
-
[1.4.3]
- Update AdGuard Home to 0.107.4
- Full changelog
- Go version was updated to prevent the possibility of exploiting the CVE-2022-23806, CVE-2022-23772, and CVE-2022-23773 vulnerabilities.
- Minor UI improvements.
- Optimistic cache now responds with expired items even if those can't be resolved again (#4254).
- Unnecessarily complex hosts-related logic leading to infinite recursion in some cases (#4216).
-
[1.4.4]
- Update AdGuard Home to 0.107.5
- Full changelog
- Go version was updated to prevent the possibility of exploiting the CVE-2022-24921 vulnerability. As the CVE page is still showing “reserved” at the time of publishing, see also golang/go#51112.
-
G guyds referenced this topic on
-
[1.4.5]
- Update AdGuard Home to 0.107.6
- Full changelog
- Go version was updated to prevent the possibility of exploiting the CVE-2022-24675, CVE-2022-27536, and CVE-2022-28327 vulnerabilities.
- Support for SVCB/HTTPS parameter dohpath in filtering rules with the dnsrewrite modifier according to the RFC draft (#4463).
- Filtering rules with the dnsrewrite modifier that create SVCB or HTTPS responses should use ech instead of echconfig to conform with the latest drafts.
