🌐 Website Issue | The VPN page doesn't mention encrypted DNS #1314

Closed
opened 2019-09-15 08:30:34 +00:00 by Mikaela · 4 comments
Mikaela commented 2019-09-15 08:30:34 +00:00 (Migrated from github.com)

Description

Screenshot from 2019-09-15 11-24-14

I think the warning should also include recommending encrypting DNS as otherwise the network administrator or attacker in local network can manipulate DNS queries or even anyone between you and the DNS server can do that.

I don't know if this would require more explanation including that if you use a VPN, your DNS goes through the VPN and using both simultaneously would require trusting both providers. And if the user is using Tor, they should let Tor/exit-nodes perform DNS to not taint circuits or send all traffic through one circuit (even while Tor exit-node is comparable to untrusted/unsecured open network).

## Description ![Screenshot from 2019-09-15 11-24-14](https://user-images.githubusercontent.com/831184/64918749-5fe91100-d7ab-11e9-8366-9d4f5abe32f6.png) I think the warning should also include recommending encrypting DNS as otherwise the network administrator or attacker in local network can manipulate DNS queries or even anyone between you and the DNS server can do that. I don't know if this would require more explanation including that if you use a VPN, your DNS goes through the VPN and using both simultaneously would require trusting both providers. And if the user is using Tor, they should let Tor/exit-nodes perform DNS to not taint circuits or send all traffic through one circuit (even while Tor exit-node is comparable to untrusted/unsecured open network). * https://www.privacytools.io/providers/dns/#icanndns
blacklight447 commented 2019-09-17 09:56:23 +00:00 (Migrated from github.com)

Im not sure about this one, the warning is already pretty long, if we make it any longer people my skip reading it at all.

Im not sure about this one, the warning is already pretty long, if we make it any longer people my skip reading it at all.
Mikaela commented 2019-09-17 17:48:05 +00:00 (Migrated from github.com)

I think encrypted DNS is an important base for https as the untrusted network could otherwise be sending users to wrong places and trigger certificate warnings.

I think encrypted DNS is an important base for https as the untrusted network could otherwise be sending users to wrong places and trigger certificate warnings.
blacklight447 commented 2019-09-23 07:57:58 +00:00 (Migrated from github.com)

Could you make a pull request to show how you would like it?

Could you make a pull request to show how you would like it?
Mikaela commented 2019-09-23 17:01:11 +00:00 (Migrated from github.com)

Sure, seems simple enough and I think HTTPS could become a link alongside it. I cannot give schedule promises though:

Sure, seems simple enough and I think HTTPS could become a link alongside it. I cannot give schedule promises though:
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1314
No description provided.