split up ad-blocking section
This commit is contained in:
parent
28b5d3c3bb
commit
723b3af75a
@ -79,6 +79,7 @@
|
|||||||
statistics?</a></li>
|
statistics?</a></li>
|
||||||
<li><a href="#firewall">Does GrapheneOS provide a firewall?</a></li>
|
<li><a href="#firewall">Does GrapheneOS provide a firewall?</a></li>
|
||||||
<li><a href="#ad-blocking">How can I set up system-wide ad-blocking?</a></li>
|
<li><a href="#ad-blocking">How can I set up system-wide ad-blocking?</a></li>
|
||||||
|
<li><a href="#ad-blocking-apps">Are ad-blocking apps supported?</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li>
|
<li>
|
||||||
@ -520,11 +521,17 @@
|
|||||||
included by the project many years ago, but it needs to be reimplemented, and it's a
|
included by the project many years ago, but it needs to be reimplemented, and it's a
|
||||||
low priority feature depending on contributors stepping up to work on it.</p>
|
low priority feature depending on contributors stepping up to work on it.</p>
|
||||||
|
|
||||||
|
<h3 id="ad-blocking-apps">
|
||||||
|
<a href="#ad-blocking-apps">Are ad-blocking apps supported?</a>
|
||||||
|
</h3>
|
||||||
|
|
||||||
<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
|
||||||
traffic through themselves to perform filtering. This approach is inherently
|
traffic through themselves to perform filtering.</p>
|
||||||
incompatible with encryption from the client to the server. The AdGuard app
|
|
||||||
works around encryption by supporting optional
|
<p>The approach of intercepting traffic is inherently incompatible with encryption
|
||||||
|
from the client to the server. The AdGuard app works around encryption by supporting
|
||||||
|
optional
|
||||||
<a href="https://kb.adguard.com/en/general/https-filtering">HTTPS interception</a> by
|
<a href="https://kb.adguard.com/en/general/https-filtering">HTTPS interception</a> by
|
||||||
having the user trust a local certificate authority, which is a security risk and
|
having the user trust a local certificate authority, which is a security risk and
|
||||||
weakens HTTPS security even if their implementation is flawless (which they openly
|
weakens HTTPS security even if their implementation is flawless (which they openly
|
||||||
@ -533,14 +540,15 @@
|
|||||||
go out of the way to allow overriding pinning with locally added certificate
|
go out of the way to allow overriding pinning with locally added certificate
|
||||||
authorities. Many of these apps only provide domain-based filtering, unlike the deeper
|
authorities. Many of these apps only provide domain-based filtering, unlike the deeper
|
||||||
filtering by AdGuard, but they're still impacted by encryption due to Private DNS
|
filtering by AdGuard, but they're still impacted by encryption due to Private DNS
|
||||||
(DNS-over-TLS). If they don't provide their own remote DNS servers, the apps require
|
(DNS-over-TLS) and require disabling the feature. They could provide their own
|
||||||
disabling Private DNS. They could provide their own DNS-over-TLS resolver to avoid
|
DNS-over-TLS resolver to avoid losing the feature, but few of the developers care
|
||||||
losing the feature, but few of the developers care enough to do that. Using the VPN
|
enough to do that.
|
||||||
service to provide something other than a VPN also means that these apps need to
|
|
||||||
provide an actual VPN implementation or a way to forward to apps providing one, and
|
<p>Using the VPN service to provide something other than a VPN also means that these
|
||||||
very few have bothered to consider this let alone implementing it. NetGuard is an one
|
apps need to provide an actual VPN implementation or a way to forward to apps
|
||||||
example implementing SOCKS5 forwarding, which can be used to forward to apps like
|
providing one, and very few have bothered to consider this let alone implementing it.
|
||||||
Orbot (Tor).</p>
|
NetGuard is an one example implementing SOCKS5 forwarding, which can be used to
|
||||||
|
forward to apps like Orbot (Tor).</p>
|
||||||
|
|
||||||
<h2 id="day-to-day-use">
|
<h2 id="day-to-day-use">
|
||||||
<a href="#day-to-day-use">Day to day use</a>
|
<a href="#day-to-day-use">Day to day use</a>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user