klavirshik
/
GoodbyeDPI
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

State Secure DNS Prevents Poisoning 

change "does not" to "can not"

because it was sounding like ISP doesn't poison on purpose, which is wrong.
This commit is contained in:
HardenedSteel 2024-05-28 06:01:55 +00:00 committed by GitHub
parent 4a82fd442d
commit 24cd3c3f10
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -80,7 +80,7 @@ Modern modesets (more stable, more compatible, faster):
-6 -f 2 -e 2 --wrong-seq --reverse-frag --max-payload
```
To check if your ISP's DPI could be circumvented, first make sure that your provider does not poison DNS answers by enabling "Secure DNS (DNS over HTTPS)" option in your browser.
To check if your ISP's DPI could be circumvented, first make sure that your provider can not poison DNS answers by enabling "Secure DNS (DNS over HTTPS)" option in your browser.
* **Chrome**: Settings → [Privacy and security](chrome://settings/security) → Use secure DNS → With: NextDNS
* **Firefox**: [Settings](about:preferences) → Network Settings → Enable DNS over HTTPS → Use provider: NextDNS