What's new in dnscrypt-proxy 1.6.0
Jan 22, 2016
- New feature: public-key based client authentication (-K), for private and commercial DNS services to securely authenticate the sender of a query no matter what the source IP address is, without altering the DNS query.
New in dnscrypt-proxy 1.4.0 (Apr 26, 2014)
- Security: versions 0.11 to 1.3.3 were vulnerable to a denial of
- service when running out of output buffer space. Reported by @iamultra.
- The resolver to use and its configuration can now be specified as a
- definition file + the name of the resolver to use. The new
- command-line options to use are --resolvers-list= and --resolver-name=. This deprecates
- --provider-key, --provider-name and --resolver-address.
- Documentation and diagnostics have been improved.
New in dnscrypt-proxy 1.3.0 (Apr 25, 2013)
- The bundled NaCl library with only reference implementations has been replaced with libsodium, leading to significant performance improvements.
- A new command-line switch, --loglevel, allows adjusting the log verbosity.
New in dnscrypt-proxy 1.2.1 (Apr 25, 2013)
- Add support for certificates split into multiple TXT records.
New in dnscrypt-proxy 1.2.0 (Apr 25, 2013)
- A pre-filter can now totally bypass the resolver and directly send a reply to the client.
- A new example plugin has been shipped: ldns-aaaa-blocking. It directly sends an empty response to AAAA queries in order to significantly speed up lookups on hosts without IPv6 connectivity (but with clients still asking for AAAA records anyway).
New in dnscrypt-proxy 1.1.0 (Apr 25, 2013)
- dnscrypt-proxy can now use plugins in order to alter/inspect queries and responses before and after they are relayed. See README-PLUGINS.markdown for more information.
- The default max payload size has been trimmed down to 1252 bytes for compatibility with some scary network setups.
- The --local-port and --resolver-port options are gone for good. They had been deprecated for a while and were undocumented since version 1.0.
- Multiple certificates are now properly handled.
- Memory leaks have been fixed, a big bad use-after-free condition has been fixed, uninitialized variables have been initialized.Upgrading is recommended, especially on Windows.