AdGuard Home versie 0.107.78 is uitgekomen. Met deze software kan er thuis een DNS-server worden opgezet om zo onder meer advertenties en malware te blokkeren op het hele netwerk, waardoor dat niet langer op elk individueel apparaat nodig is. Het is daarmee dus vergelijkbaar met Pi-hole. AdGuard Home werkt op een machine met Windows, macOS, Linux of FreeBSD, is ook in staat om tegen phishing te beschermen en heeft parental control. Op ons eigen forum kan over het programma worden gediscussieerd. In deze uitgave zijn de volgende veranderingen en verbeteringen aangebracht:
AdGuard Home 0.107.78Security, security, security, security, security! No, we do not have Steve Ballmer for CEO, but we took a page out of his playbook to draw attention to what we think is one of the most important aspects of developing AdGuard Home — security. This update is a good illustration of that: security-related changes take up over half of the changelog, and it’s not a small one.
SecurityAdded
- AdGuard Home is now more resistant to JIGGLE attacks. This is GHSA-p5f5-3p5g-rfjw.
- AdGuard Home now validates responses from DoH upstreams more strictly. This is GHSA-4qjf-2hgm-92q6.
- QUIC connections are now protected from unbounded reads. This is GHSA-qr92-rwvw-mhgh and GHSA-cccx-2r6r-m9r4.
- AdGuard Home now validates responses from DNSCrypt upstreams more strictly.
- The H2C connection establishment via HTTP/1.1 request upgrade is no longer supported. See RFC 9113.
- Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.5.
- The size of rulelists is limited. This is necessary to prevent a user's machine from becoming overloaded if the filter source misbehaves.
Changed
- Improved updater logging to give users more insight into the problem with version updating (#8410).
Configuration changes
- The interval of filter updates can now be set to any number of hours between
0and8760(365 days) in the configuration file.Fixed
- The
filteringobject of the YAML configuration now includes a new property,max_http_size, which defines the maximum size of the HTTP request for rulelists. To disable the limitation, set a large size, such as1 TB.

:strip_icc():strip_exif()/u/1650152/crop677eca9974266.jpg?f=community)
:strip_icc():strip_exif()/u/384715/Ministry_Of_Sound_Logo_60.jpg?f=community)
:strip_exif()/u/427742/crop6a410145d63e6.gif?f=community)
:strip_exif()/u/69039/MetallicA.gif?f=community)
:strip_icc():strip_exif()/u/961/crop69b8f434281b1_cropped.jpg?f=community)