There were two `ls -l dnscrypt-proxy-*.tar.gz dnscrypt-proxy-*.zip`
commands in `.travis.yml`, one in the `script`(build) phase, one in the
`after_deploy` phase, they were actually duplicated.
As deployment job won't create any new files, and the command isn't part
of the steps to build artifacts, but to confirm/list the built files,
this action looks more suitable to be placed in the `after_success`, to
be separated with the build commands, and the duplicated one in the
`after_deploy` phase could be removed.
* 'master' of github.com:jedisct1/dnscrypt-proxy:
blocked_query_response takes the format 'a:<IPv4>,aaaa:<IPv6>' for IP responses
fold 'refused_code_in_responses' and 'respond_with_ip' options into a new option 'blocked_query_response'
add new option: 'respond_with_ip'
Added financial contributors to the README
Windows doesn't seem to like this address.
Also default to the fallback resolver IP if there is one and
no netprobe_address option in the configuration file.
Fix netprobe_timeout = -1 by the way
Write at least 1 byte. This ensures that sockets are ready to use for writing.
Windows specific: during the system startup, sockets can be created but the underlying buffers may not be setup yet. If this is the case Write fails with WSAENOBUFS: "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
This fixes: https://github.com/jedisct1/dnscrypt-proxy/issues/841
Not all URLs are extracted from the complicated csv file.
However, they do offer a txt file for the same list, which does work correctly with the current regex:
https://www.malwaredomainlist.com/forums/index.php?topic=3270.0
This url replacement pull request is easier than rewriting the entire regex (which then breaks other lists).