Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dns0 has some logging #2484

Closed
2 tasks done
jonaharagon opened this issue Apr 4, 2024 · 5 comments · Fixed by #2509
Closed
2 tasks done

dns0 has some logging #2484

jonaharagon opened this issue Apr 4, 2024 · 5 comments · Fixed by #2509
Labels
c:providers service providers and similar centralized/federated services t:correction content corrections or errors

Comments

@jonaharagon
Copy link
Member

Affected page

https://www.privacyguides.org/en/dns/#recommended-providers

Description

Table should note that bulk data is collected for threat intelligence (see Cloudflare DNS for example of how to format such a note)

Sources

https://discuss.privacyguides.net/t/nextdns-logging-is-opt-out-not-opt-in-as-stated-on-pgs-dns-resolvers-recommendations-page/17206/57

Before submitting

  • I am reporting something that is verifiably incorrect, not a suggestion or opinion.
  • I agree to the Community Code of Conduct.
@jonaharagon
Copy link
Member Author

We should add a specific logging criteria on this page to note what is and isn’t acceptable data to store too

@jonaharagon jonaharagon added c:providers service providers and similar centralized/federated services t:correction content corrections or errors labels Apr 4, 2024
@privacyguides-bot
Copy link
Collaborator

This issue has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/nextdns-logging-is-opt-out-not-opt-in-as-stated-on-pgs-dns-resolvers-recommendations-page/17206/63

@dngray
Copy link
Member

dngray commented Apr 4, 2024

I think we should clearly state that logging relates to matching clients with queries, that is after all what most people are going to care about.

"If I go to this website, is anyone going to know or have a record of that?"

Basic metrics on how much of something happens that can't be tied back to a user shouldn't count as logging. We should probably switch quad9 to no logs based on their extensive privacy policy.

If anonymity is in your threat model, then anonymous technology needs to be employed. The assumption here is you wouldn't even trust a privacy policy.

@privacyguides-bot
Copy link
Collaborator

This issue has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/nextdns-logging-is-opt-out-not-opt-in-as-stated-on-pgs-dns-resolvers-recommendations-page/17206/66

@ignoramous
Copy link

rethinkdns dev here

clearly state that logging relates to matching clients with queries

With DNS-over-TLS and especially DNS-over-HTTPS, logging protocol-relevant information that's not PII to pin-point clients becomes "easier". I don't suspect most DNS resolvers are nefarious, but a mere mention of "no PII" in policy document shouldn't inform PrivacyGuides' judgement if "matching clients with queries" is the criteria.

anonymous technology needs to be employed

Providers that support ODoH and DNSCrypt v3 must be looked at for recommendations, imo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:providers service providers and similar centralized/federated services t:correction content corrections or errors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants