Indiscriminate fallback to system-/bootstrap-resolvers in case of error/interference/disruption? #3166
Closed
cobratbq
started this conversation in
Potential issues
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It seems that the normal code-path for name-resolution always falls back to system- and/or bootstrap-resolvers in case of failure when using the configured (secure) DNS-resolution.
dnscrypt-proxy/dnscrypt-proxy/xtransport.go
Line 580 in 64edfa3
This is a (virtually) silent drop of privacy and confidentiality that, in case of DNSCrypt, would be trivial to detect and abuse.
Am I reading this wrong? (Case
erris non-nil.)edit: I created #3165 by referencing a code-line in a new issue, but now Github is annoyed :-P
edit: the documentation implies that the bootstrap-resolvers are only used to acquire sufficient information to set up a connection with the secure DNS resolvers, whether DNSCrypt or DoH. It seems that this is currently not the case.
Beta Was this translation helpful? Give feedback.
All reactions