Indicate which DNS providers support DoT over port 443 #1178
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1178
Loading…
Reference in New Issue
No description provided.
Delete Branch "indicate-443-port-for-dot-providers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
This PR adds a tooltip to the providers who support DoT over port 443 in addition to the expected port 853. This is an important indication because like DoH, DoT/443 makes eavesdropping more difficult for third parties and provides the benefit of not easily being blocked by firewalls compared to 853.
Resolves: #none
Check List
I have read and understand CONTRIBUTING.md.
I have listed the source code for this project in source_code.md.This project is free/libre software.This project has an associated discussion.(via Wire chat)Code Repository (if applicable): N/A
Deploy preview for privacytools-io ready!
Built with commit
8c81461501
https://deploy-preview-1178--privacytools-io.netlify.com
It's a good beginning, but:
Hmm, these are good points 🤔
Yeah that makes sense, what if I also bold the text instead of relying on just a color change? Will push an update to try it.
Okay, I'll give those three providers' protocol field a custom value so they're grouped together while everything else sorts by length? I'll push an update for this.
Good callout; will do 👍
That's a good question; from my understanding, couldn't your ISP distinguish TLS from HTTPS traffic based on traffic analysis + connection metadata?
Looks great 👍
I wonder if green is the best color choice, does it imply that configuration is more secure than others? I'd probably prefer using
text-info
or maybetext-primary
. Or even just black with bold text.I've removed the color; you're right; DoT/443 isn't necessarily more secure from my understanding, but doesn't stand out as much. In other words, it's more difficult to eavesdrop on and block.
@Mikaela this makes me think our description for DoT/443 in the terms could mention that eavesdropping is more difficult. Currently it says:
What do you mean by eavesdropping? The queries are encrypted from you to the DNS server and no one else can read them.
@Mikaela ah sorry, by eavesdropping, I mean DoT/443 could potentially be more difficult for your ISP/3rd parties to analyze and detect than DoT/853, yeah?
Possibly yes, but I am not comfortable making that claim personally until someone wiser tells me so
As I went jabbering about this on the forum could we have a review and merge? :)
What about adding question mark next do DoT?
It is hard to tell that there is hidden info.