How to install DNSCrypt

[tommyb.]

.
WHERE are the *.deb files?
.
.
Seems like the link leads to an empty github repository (files on github are gone) and on "dnscrypt.org" i find only some for compilation
.
.
.
I guess i keep using the old ones then ....

[xenopeek]

Thanks tommyb., I've updated the first post in this topic to reflect that the tutorial is currently not usable due to the missing .deb files. Compiling from source should work (and is detailed on their website), but it's not high on my priority list to figure this all out right now. Might get around to it later

[metalbolic]

Good afternoon!!!

Guys, I follow the tutorial to the letter, but I received various messages of errors, like that:

The script you are attempting to invoke has been converted to an Upstart
job, but --daemonize is not supported for Upstart jobs.

start: Unknown job: dnscrypt-proxy

How do resolve this?

thanks, in advance!!

[tommyb.]

Thanks tommyb., I've updated the first post in this topic to reflect that the tutorial is currently not usable due to the missing .deb files. Compiling from source should work (and is detailed on their website), but it's not high on my priority list to figure this all out right now. Might get around to it later

Ok, for those interested i have the needed files in my dropbox public folder (dnscrypt 1.10, 0.94, 0.12) https://www.dropbox.com/sh/n14ywb4kqbbhaso/QoDHgovZX6. Just installed them on LinuxMint14 Mate 64bit

[jdthood]

10. Reconfigure Network Manager to use DNSCrypt
Open Network Connections from the menu. On the Wired or Wireless tab highlight your active Internet connection. Click "Edit". On the IPv4 Settings tab, set Method to "Automatic (DHCP) addresses only" and set DNS servers to "127.0.0.1". Click "Save". Click "Close".

This is not how the "DNS servers" field is supposed to be used. The DNS server addresses listed in that field are supposed to be the addresses of servers accessible over that connection.

What you really want to do is to reconfigure the resolver so that it only uses dnscrypt-proxy and not any other nameservers known to the system, including nameservers known to NetworkManager.

Sooner or later dnscrypt-proxy will be packaged for Debian (http://bugs.debian.org/692320) and shortly there will be support for dnscrypt-proxy in dnsmasq (ugs.debian.org/709179).

Until that work is done, on a system with resolvconf, the best thing to do is to put

Code: Select all

nameserver 127.0.0.2  # dnscrypt-proxy's listen address

in /etc/resolvconf/resolv.conf.d/head.