diff options
| author | Joachim Fasting <joachifm@fastmail.fm> | 2014-11-11 20:12:28 +0100 |
|---|---|---|
| committer | Joachim Fasting <joachifm@fastmail.fm> | 2014-11-11 22:47:19 +0100 |
| commit | 52f0553209ad8f102eefd0d46ad336ff95f398be (patch) | |
| tree | f860c01b9ec19115cdca5812eec28b65818b66a2 /pkgs/development/python-modules/GitPython | |
| parent | 216ed76821fdb92443498920da6e8d88af451f9d (diff) | |
Add dnscrypt-proxy service
The dnscrypt-proxy service relays regular DNS queries to
a DNSCrypt enabled upstream resolver.
The traffic between the client and the upstream resolver is
encrypted and authenticated, which may mitigate the risk of
MITM attacks and third-party snooping (assuming a trustworthy
upstream).
Though dnscrypt-proxy can run as a standalone DNS client,
the recommended setup is to use it as a forwarder for a
caching DNS client.
To use dnscrypt-proxy as a forwarder for dnsmasq, do
```nix
{
# ...
networking.nameservers = [ "127.0.0.1" ];
networking.dhcpcd.extraConfig = "nohook resolv.conf";
services.dnscrypt-proxy.enable = true;
services.dnscrypt-proxy.localAddress = "127.0.0.1";
services.dnscrypt-proxy.port = 40;
services.dnsmasq.enable = true;
services.dnsmasq.extraConfig = ''
no-resolv
server=127.0.0.1#40
listen-address=127.0.0.1
'';
# ...
}
```
Diffstat (limited to 'pkgs/development/python-modules/GitPython')
0 files changed, 0 insertions, 0 deletions
