dnscrypt-proxy-2.0.17_5

Not a significant release, just small improvements for development.

• The generate-domains-blacklist.py script is now directly sourced from the git archive rather than checked-in to this repository
• The git archive name now includes the project name to avoid conflicting file names.

dnscrypt-proxy-2.0.17_4

Fix permission issue on SRM

dnscrypt-proxy-2.0.17_3

There was a condition that could occur when getting a new version of the python script would fail and create a 0 byte file

Should fix SynoCommunity#3468 (comment)

dnscrypt-proxy-2.0.17_2

This release fixes where generating the blacklist would appear not have done anything. The reason for this is that the GUI was not updated when the blacklist was already loaded. Previously using the browser reload button would also overwrite the blacklist file with old content.

Thanks @s1mwest for reporting this issue

dnscrypt-proxy-2.0.17_1

This release fixes many issues when running the package under DSM. Today was is the first time I was able to test the package under DSM. Sorry for the inconvenience, I didn't think that the difference between SRM and DSM was big enough to test for both.

The package was tested working under SRM 1.2 (ARM) and DRM 6.1 (x64)

dnscrypt-proxy-2.0.17

• Update dnscrypt-proxy to 2.0.17
• This fixes previous problems when dropping privileges / running as a different user.
• Feature: The package can now be installed while offline.
• Use DNS forwarding through dnsmasq, this should fix instances where some queries related to local networking where not answered and fix bonjour services. This only applies when dhcpd is running.
• Updated go to 1.11.1

dnscrypt-proxy-2.0.16

• Rename /etc/dhcpd/dhcpd-custom-custom.conf to /etc/dhcpd/dhcpd-dnscrypt-dnscrypt.conf
• By default the 2.0.16 new user_name option is enabled. This is to run the main service as a non-root user. This option will use slightly more system resources since both a root and one non-root user process is running. The root process is only run as a supervisor to healthcheck the non-root process and to create the network sockets.

This can be turned off by commenting the user_name option after install.
Users updating will need to enable the option manually. (The default user_name is svc-dncrypt-proxy or sc-dncrypt-proxy depending on the DSM/RSM version)

EDIT: Known Issues:
The new user_name option courses problems when restarting the service. See DNSCrypt/dnscrypt-proxy#547

dnscrypt-proxy-2.0.15_test_don_t_use

Build from SynoCommunity/spksrc:master

SynoCommunity#3365 (comment)

dnscrypt-proxy-2.0.15_8

Corrected terminology and capitalisation

• DNS-over-HTTP/2 -> DNS-over-HTTPS - the relevant RFC is named HTTPS not HTTP/2
• DNSCrypt-proxy -> dnscrypt-proxy - DNSCrypt/dnscrypt-proxy#533
• dnscrypt -> DNSCrypt - DNSCrypt/dnscrypt-proxy#533

No bugfixes or new features just the above mentioned cosmetic changes.

dnscrypt-proxy-2.0.15_7

• Fix invalid JSON in src/conf/resource
  • SynoCommunity#3357 (comment)