diff options
| author | Daniel Micay <danielmicay@gmail.com> | 2020-02-28 21:47:22 -0500 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2020-02-28 21:47:22 -0500 |
| commit | bd93da0d4722c24fb82121eafae32506168a60b2 (patch) | |
| tree | f7ba77ae3c47a7ce6271906741eab748b0c5f3be /static | |
| parent | 17ed0acd2653fe22a902ad8fed03ce1a608e631b (diff) | |
clarification about DHCP
Diffstat (limited to 'static')
| -rw-r--r-- | static/faq.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/static/faq.html b/static/faq.html index 7954b391..ab6b74cb 100644 --- a/static/faq.html +++ b/static/faq.html @@ -368,11 +368,11 @@ <p>By default, in the automatic mode, the Private DNS feature provides opportunistic encryption by using DNS-over-TLS when supported by the DNS server IP addresses - provided by the network or the static IP configuration. Opportunistic encryption - provides protection against a passive listener, not an active attacker, since they can - force falling back to unencrypted DNS by blocking DNS-over-TLS. In the automatic mode, - certificate validation is not enforced, as it would provide no additional security and - would reduce the availability of opportunistic encryption.</p> + provided by the network (DHCP) or the static IP configuration. Opportunistic + encryption provides protection against a passive listener, not an active attacker, + since they can force falling back to unencrypted DNS by blocking DNS-over-TLS. In the + automatic mode, certificate validation is not enforced, as it would provide no + additional security and would reduce the availability of opportunistic encryption.</p> <p>When Private DNS is explicitly enabled, it uses authenticated encryption without a fallback. The authentication is performed based on the hostname of the server, so it |
