security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

mention plans to add back local DNS blacklist

Browse Source
This commit is contained in:
Daniel Micay 2020-03-02 07:45:47 -05:00
parent 2860ce612b
commit 57696841f0
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
static/faq.html
View File

@ -513,7 +513,12 @@
ad-blocking as part of DNS resolution. You can do this by ad-blocking as part of DNS resolution. You can do this by
<a href="#custom-dns">choosing a Private DNS (DNS-over-TLS) server</a> with support <a href="#custom-dns">choosing a Private DNS (DNS-over-TLS) server</a> with support
for blocking ad domains. As an example, AdGuard DNS can be used by setting for blocking ad domains. As an example, AdGuard DNS can be used by setting
<code>dns.adguard.com</code> as the Private DNS domain.</p> <code>dns.adguard.com</code> as the Private DNS domain. In the future, GrapheneOS
plans on adding back <a
href="https://github.com/GrapheneOS/os_issue_tracker/issues/184">an efficient
user-defined blacklist for the local DNS resolver</a>. An implementation of this used
to be included, but it needs to be reimplemented, and it's a low priority feature
depending on contributors stepping up to work on it.</p>
<p>Content filtering apps are fully compatible with GrapheneOS, but they have serious <p>Content filtering apps are fully compatible with GrapheneOS, but they have serious
drawbacks and are not recommended. These apps use the VPN service feature to route drawbacks and are not recommended. These apps use the VPN service feature to route