mirror of
https://github.com/DNSCrypt/dnscrypt-proxy.git
synced 2025-03-04 10:24:40 +01:00
http -> https
Frank Denis
parent
a02ac63f48
commit
4ca3b5cec4
5 changed files with 18 additions and 18 deletions
|
|
@ -107,7 +107,7 @@ If all went well, $GOPATH/$GOOS-$GOARCH/dnscrypt-proxy should contain built dnsc
|
|||
|
||||
### Adding entitlements
|
||||
|
||||
Before the binary can be ran on your iOS device, it needs to be [signed](http://www.saurik.com/id/8).
|
||||
Before the binary can be ran on your iOS device, it needs to be [signed](https://www.saurik.com/codesign.html).
|
||||
The following steps assume that they are being performed on the iOS device itself as root.
|
||||
|
||||
1. Install ldid using Cydia or `apt-get`.
|
||||
|
|
@ -115,7 +115,7 @@ The following steps assume that they are being performed on the iOS device itsel
|
|||
2. Save the following (in UTF-8 as the first line points out) as ent.xml:
|
||||
```
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
|
||||
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://www.apple.com/DTDs/PropertyList-1.0.dtd">
|
||||
<plist version="1.0">
|
||||
<dict>
|
||||
<key>get-task-allow</key>
|
||||
|
|
@ -171,4 +171,4 @@ chmod 644 /etc/dnscrypt-proxy/*
|
|||
|
||||
6. Finally, configure the DNS server for your Wi-Fi connection to be 127.0.0.1 inside the iDevice's settings.
|
||||
|
||||
If all went well, dnscrypt-proxy should start at boot (or when your semi-tethered jailbreak is activated if that's the case).
|
||||
If all went well, dnscrypt-proxy should start at boot (or when your semi-tethered jailbreak is activated if that's the case).
|
||||
|
|
|
|||
4
Home.md
4
Home.md
|
|
@ -13,7 +13,7 @@ This is the official wiki for dnscrypt-proxy. Anybody can update its content and
|
|||
If you have contributed, feel free to add your details below:
|
||||
|
||||
- [@acejacek](https://github.com/acejacek) — Jacek
|
||||
- [@afonari](https://github.com/afonari) — [Alexandr Fons](http://afonari.com/)
|
||||
- [@afonari](https://github.com/afonari) — [Alexandr Fons](https://afonari.com/)
|
||||
- [@AmirHosseinKarimi](https://github.com/AmirHosseinKarimi) — [Amir Hossein Karimi](https://www.vira.studio/)
|
||||
- [@B00ze64](https://github.com/B00ze64) — Sylvain
|
||||
- [@balupton](https://balupton) — [Benjamin Lupton](https://balupton.com)
|
||||
|
|
@ -21,7 +21,7 @@ If you have contributed, feel free to add your details below:
|
|||
- [@chuacw](https://github.com/chuacw) — [Chee Wee Chua](https://chuacw.ath.cx/blogs/chuacw/default.aspx?r=1221)
|
||||
- [@DaCoolX](https://github.com/DaCoolX)
|
||||
- [@evilvibes](https://github.com/evilvibes) — [Andrew](https://evilvibes.com/)
|
||||
- [@fahadshery](https://github.com/fahadshery) — [Fahad Usman](http://fahadusman.com/computer-network-security/recon/dns-tips-and-tricks/encrypting-dns-traffic/)
|
||||
- [@fahadshery](https://github.com/fahadshery) — Fahad Usman
|
||||
- [@JayBrown](https://github.com/JayBrown) — [Joss Brown](https://zbd.gg/lcars)
|
||||
- [@jedisct1](https://github.com/jedisct1) — [Frank Denis](https://prettysimpleimages.com/)
|
||||
- [@L8X](https://github.com/L8X) — Madilyn
|
||||
|
|
|
|||
|
|
@ -232,7 +232,7 @@ It just informs you that the `dnscrypt-proxy.plist` file has been added to macOS
|
|||
|
||||
**— DNSMasq**
|
||||
|
||||
See chapter 'Making things go fast - IPv6 blocking' for [DNSmasq](http://www.thekelleys.org.uk/dnsmasq/doc.html).
|
||||
See chapter 'Making things go fast - IPv6 blocking' for [DNSmasq](https://www.thekelleys.org.uk/dnsmasq/doc.html).
|
||||
|
||||
### Control dnscrypt-proxy from the menu bar
|
||||
|
||||
|
|
@ -253,7 +253,7 @@ It is quite annoying, because at the same time macOS doesn't allow to set a spec
|
|||
Fortunately, `mDNSResponder`'s DNS proxy can be disabled in its configuration file:
|
||||
`/System/Library/LaunchDaemons/com.apple.mDNSResponder.plist`
|
||||
|
||||
As this file is in `/System`, changing it first requires to [disable SIP](http://apple.stackexchange.com/questions/208478/how-do-i-disable-system-integrity-protection-sip-aka-rootless-on-os-x-10-11).
|
||||
As this file is in `/System`, changing it first requires to [disable SIP](https://apple.stackexchange.com/questions/208478/how-do-i-disable-system-integrity-protection-sip-aka-rootless-on-os-x-10-11).
|
||||
|
||||
Change
|
||||
|
||||
|
|
|
|||
|
|
@ -2,22 +2,22 @@
|
|||
|
||||
## Enabling the Community Repository
|
||||
|
||||
dnscrypt-proxy is in the 'community' repository which needs to be enabled in `/etc/apk/respositories` by removing the comment `#` on the appropriate line e.g.
|
||||
dnscrypt-proxy is in the 'community' repository which needs to be enabled in `/etc/apk/respositories` by removing the comment `#` on the appropriate line e.g.
|
||||
|
||||
```text
|
||||
# main and community enabled, testing disabled on the 'edge' branch
|
||||
http://alpine.mirror.wearetriple.com/edge/main
|
||||
http://alpine.mirror.wearetriple.com/edge/community
|
||||
#http://alpine.mirror.wearetriple.com/edge/testing
|
||||
https://alpine.mirror.wearetriple.com/edge/main
|
||||
https://alpine.mirror.wearetriple.com/edge/community
|
||||
#https://alpine.mirror.wearetriple.com/edge/testing
|
||||
```
|
||||
|
||||
If you're not running on 'edge' then you might see the version numbers instead
|
||||
|
||||
```text
|
||||
# main and community enabled, testing disabled on the 'V3.9' branch
|
||||
http://alpine.mirror.wearetriple.com/V3.9/main
|
||||
http://alpine.mirror.wearetriple.com/V3.9/community
|
||||
#http://alpine.mirror.wearetriple.com/V3.9/testing
|
||||
https://alpine.mirror.wearetriple.com/V3.9/main
|
||||
https://alpine.mirror.wearetriple.com/V3.9/community
|
||||
#https://alpine.mirror.wearetriple.com/V3.9/testing
|
||||
```
|
||||
|
||||
## Installation
|
||||
|
|
|
|||
|
|
@ -172,6 +172,8 @@ openwrt > dnscrypt-proxy -resolve google.com
|
|||
```
|
||||
`Resolver IP` should not belong to your ISP. You can verify whose network an IP address is on [IPtoASN](https://iptoasn.com).
|
||||
|
||||
This will also detect if the server supports DNSSEC, print its real IP address, and check if it returns fake responses for nonexistent domains.
|
||||
|
||||
#### Check that processes on the router use `dnsmasq`:
|
||||
|
||||
```sh
|
||||
|
|
@ -191,8 +193,6 @@ You should make sure that any reported name or IP is **NOT** associated with the
|
|||
|
||||
If you see the ISP presence in the test results, something is wrong with the configuration, since it's bypassing your `dnscrypt-proxy` provider.
|
||||
|
||||
[DNSSEC resolver test](http://dnssec.vs.uni-due.de/) determines whether your DNS resolver validates DNSSEC signatures.
|
||||
The following site can check if the resolver can connect to upstream servers using IPv6 IPv6 and does DNSSEC validation: https://en.internet.nl/connection/
|
||||
|
||||
You can also use this site to test both your IPV4 & IPV6 & DNSSEC settings: https://en.internet.nl/connection/
|
||||
|
||||
Cloudflare also has a great site for checking your configuration: https://www.cloudflare.com/ssl/encrypted-sni/
|
||||
Cloudflare also has a web page to check that you're using their resolvers: https://www.cloudflare.com/ssl/encrypted-sni/
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue