AdGuard Home v0.107.79
- Bootstrap servers configuration now supports comments
- New property "language" in POST /control/install/check_config and POST /control/install/configure HTTP APIs
- The user is able to remove the static lease's hostname via the HTTP API
- The edge channel has been switched to the new UI and versioning scheme
- DNS64 treating unresolved CNAME/DNAME answers as the end of resolution chain
- Blocked requests without an EDNS(0) OPT record
- strict_sni_check is now deprecated
- Go version has been updated to prevent the possibility of exploiting Go vulnerabilities fixed in 1.26.6
- AdGuard Home is now more resistant to resource exhaustion attacks when using DNS-over-QUIC
From AdGuard Home
It’s not always the big issues: sometimes what you need is a few fixes and tweaks to pump up the overall stability 🔩
Full changelog
See also the v0.107.79 GitHub milestone.
Security
-
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.6.
-
AdGuard Home is now more resistant to resource exhaustion attacks when using DNS-over-QUIC.
This is GHSA-w6v6-f44j-3rj2. We thank @ATinyShoe for reporting this security issue.
Added
-
Bootstrap servers configuration now supports comments.
-
New property
"language"inPOST /control/install/check_configandPOST /control/install/configureHTTP APIs. -
The user is able to remove the static lease's hostname via the HTTP API.
Changed
- The
edgechannel has been switched to the new UI and versioning scheme.
Deprecated
strict_sni_checkis now deprecated.
Fixed
-
DNS64 treating unresolved
CNAME/DNAMEanswers as the end of resolution chain (#7514). -
Blocked requests without an EDNS(0) OPT record (#8183).