[docs] Added the remaining parts to the modern changelog file

This commit is contained in:
quindecim 2022-05-01 23:35:23 +02:00 committed by GitHub
parent 06e7906c29
commit 5c4ad9c4e6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 344 additions and 0 deletions

View File

@ -221,3 +221,347 @@ forced to use TCP.
### Changed
- `Magisk 20+` required.
## 2.0.42-3
### Added
- `DROP` properly `IPv6` queries in `post-fs-data.sh` file (no more DNS leaks this time).
## 2.0.42-2
### Added
- 2nd attempt to `DROP` `IPv6` queries in `post-fs-data.sh` file.
## 2.0.42-1
### Added
- 1st attempt to `DROP` `IPv6` queries in `post-fs-data.sh` file.
- `whitelist.txt` file (as placeholder, once the blacklist goes public).
- `meganerd` resolver (Non-logging, non-filtering, supports DNSSEC by MegaNerd.nl).
- Optimized relays.
### Changed
- Moved all the example documents into `dnscrypt-proxy/example-docs` folder (the remaining example documents must be deleted manually).
### Removed
- `dnscrypt.nl-ns0` resolver.
- `dnscrypt.one` resolver.
- `ffmuc.net` resolver.
- `publicarray-au2` resolver.
## 2.0.42
### Upstream
- The current versions of the `dnsdist` load balancer (presumably used
by quad9, cleanbrowsing, qualityology, freetsa.org, ffmuc.net,
opennic-bongobow, sth-dnscrypt-se, ams-dnscrypt-nl and more)
is preventing queries over 1500 bytes from being received over UDP.
Temporary workarounds have been introduced to improve reliability
with these resolvers for regular DNSCrypt. Unfortunately, anonymized
DNS cannot be reliable until the issue is fixed server-side. `dnsdist`
authors are aware of it and are working on a fix.
- New option in the `[anonymized_dns]` section: `skip_incompatible`,
to ignore resolvers incompatible with Anonymized DNS instead of
using them without a relay.
- The server latency benchmark is faster while being able to perform
more retries if necessary.
- Continuous integration has been moved to GitHub Actions.
### Added
- Set `skip_incompatible` option from `false` to `true` to ignore servers incompatible with anonymization.
## 2.0.41
### Upstream
- Precompiled binaries for armv5, armv6 and armv7 are available.
The default arm builds were not compatible with older CPUs when
compiled with Go 1.14. mips64 binaries are explicitly compiled with
softfloat to improve compatibility.
- Quad9 seems to be only blocking fragmented queries over UDP for
some networks. They have been removed from the default list of broken
resolvers; runtime detection of support for fragments should now do
the job.
- Runtime detection of support for fragments was actually enabled.
## 2.0.40
### Upstream
- Servers blocking fragmented queries are now automatically detected.
- The server name is now only present in query logs when an actual upstream servers was required to resolve a query.
- TLS client authentication has been added for DoH.
- The Firefox plugin is now skipped for connections coming from the local DoH server.
- DoH RTT computation is now more accurate, especially when CDNs are in the middle.
- The forwarding plugin is now more reliable, and handles retries over TCP.
## 2.0.39-2
### Removed
- `blacklist.txt` file (too many false positives, will be added back in the future, when it reaches a more stable level).
## 2.0.39-1
### Added
- Automatic redirection in `post-fs-data.sh` file. (no more 3rd-party apps are required to start the service).
- Substrings and wildcards into `blacklist.txt` file and updated to `2020.03.19`.
### Removed
- `ibksturm` resolver.
- `dnswarden-dc1`, `dnswarden-dc2`, `dnswarden-dc3`, resolvers.
## 2.0.39
### Upstream
- The Firefox Local DoH service didn't properly work in version 2.0.38;
this has been fixed. Thanks to Simon Brand for the report!
## 2.0.38
### Upstream
- Entries from lists (forwarding, blacklists, whitelists) now support
inline comments.
- Reliability improvement: queries over UDP are retried after a timeout
instead of solely relying on the client.
- Reliability improvement: during temporary network outages, cached records
are now served even if they are stale.
- Bug fix: SOCKS proxies and DNS relays can be combined.
- New feature: multiple fallback resolvers are now supported (see the
new `fallback_resolvers` option. Note that `fallback_resolver` is
still supported for backward compatibility).
- Windows: the service can be installed with a configuration file
stored separately from the application.
- Security (affecting DoH): precompiled binaries of `dnscrypt-proxy 2.0.37` are
built using `Go 1.13.7` that fixes a TLS certificate parsing issue present in
previous versions of the compiler.
### Added
- `dnswarden-dc3` (DnsCrypt protocol . Non-logging, supports DNSSEC. By https://dnswarden.com).
### Changed
- `Magisk 19+` required.
- Updated `blacklist.txt` to `2020.01.30`.
### Fixed
- `dnscrypt-proxy` service doesn't detect the config file.
## 2.0.36
### Upstream
- New option: `block_undelegated`. When enabled, `dnscrypt-proxy` will
directly respond to queries for locally-served zones (https://sk.tl/2QqB971U)
and nonexistent zones that should have been kept local, but are frequently
leaked. This reduces latency and improves privacy.
- Conformance: the `DO` bit is now set in synthetic responses if it was
set in a question, and the `AD` bit is cleared.
- The `miegkg/dns` module was updated to version 1.1.26, that fixes a
security issue affecting non-encrypted/non-authenticated DNS traffic. In
`dnscrypt-proxy`, this only affects the forwarding feature.
### Added
- `dnscrypt.one` resolver (DNSSEC / no logs / uncensored, Germany (Nuremberg), https://dnscrypt.one/).
- Optimized relays.
### Changed
- Updated `blacklist.txt` to `2019.12.22`.
## 2.0.35
### Upstream
- New option: `block_unqualified` to block `A`/`AAAA` queries with
unqualified host names. These will very rarely get an answer from upstream
resolvers, but can leak private information to these, as well as to root
servers.
- When a `CNAME` pointer is blocked, the original query name is now logged
along with the pointer. This makes it easier to know what the original
query name, so it can be whitelisted, or what the pointer was, so it
can be removed from the blacklist.
### Added
- `scaleway-ams` resolver (DNSSEC/Non-logged/Uncensored in Amsterdam- ARM server donated by Scaleway.com) Maintained by Frank Denis- https://fr.dnscrypt.info).
- `ffmuc.net` resolver (An open DNSCrypt resolver operated by Freifunk Munich with nodes in DE. https://ffmuc.net/).
- Optimized relays.
### Changed
- Updated `blacklist.txt` to `2019.12.09`.
### Fixed
- Backup an existing `.toml` file before proceed with the installation.
## 2.0.34
### Upstream
- Blacklisted names are now also blocked if they appear in `CNAME`
pointers.
- `dnscrypt-proxy` can now act as a local DoH *server*. Firefox can
be configured to use it, so that ESNI can be enabled without bypassing
your DNS proxy.
### Added
- `ibksturm`- dnscrypt-server (nginx- encrypted-dns- unbound backend), DNSSEC / Non-Logged / Uncensored, OpenNIC and Root DNS-Zone- Hosted in Switzerland by ibksturm, aka Andreas Ziegler).
- `blacklist.txt` file to prevent `CNAME Cloaking` tracking feature.
- Optimized relays.
### Removed
- `charis` and `suami` resolvers.
## 2.0.33
### Upstream
- Fixes an issue that caused some valid queries to return `PARSE_ERROR`.
- On certificate errors, the server name is now logged instead of the
provider name, which is generally more useful.
- IP addresses for DoH servers that require DNS lookups are now cached
for at least 12 hours.
- `ignore_system_dns` is now set to `true` by default.
- A workaround for a bug in Cisco servers has been implemented.
- A corrupted or incomplete resolvers list is now ignored, keeping the
last good known cached list until the next update. In addition, logging was
improved and unit tests were also added. Awesome contribution from William
Elwood, thanks!
- On Windows, the network probe immediately returned instead of blocking
if `netprobe_timeout` was set to `-1`. This has been fixed.
- Expired cached IP addresses now have a grace period, to avoid breaking the
service if they temporarily can't be refreshed.
- On Windows, the service now returns immediately, solving a long-standing
issue when initialization took more than 30 seconds ("The service did not
respond to the start or control request in a timely fashion"). Fantastic
work by Alison Winters, thanks!
- The `SERVER_ERROR` error code has been split into two new error codes:
`NETWORK_ERROR` (self-explanatory) and `SERVFAIL` (a response was returned,
but it includes a `SERVFAIL` error code).
- Responses are now always compressed.
### Added
- `v.dnscrypt.uk-ipv4` (DNSCrypt v2, no logs, uncensored, DNSSEC. Hosted in London UK on Vultr- https://www.dnscrypt.uk).
- Optimized relays (set to use other providers different from the main one).
## 2.0.31
### Upstream
- This version fixes a startup issue introduced in version 2.0.29, on systems for which the service cannot be automatically installed (such as OpenBSD and FreeBSD). Reported by @5ch17 and Vinícius Zavam, and fixed by Will Elwood, thanks!
- This version fixes two regressions introduced in version 2.0.29: DoH server couldn't be reached over IPv6 any more, and the proxy couldn't be interrupted while servers were being benchmarked.
### Changed
- Another way to backup an existing `.toml` file (the old configuration is now backed up with `year-month-day-hour-minute.bak` suffix, thanks to @lindroidux).
## 2.0.29
### Upstream
- Support for Anonymized DNS has been added!
- Wait before stopping, fixing an issue with Unbound (thanks to Vladimir Bauer)
- DNS stamps are now included in the `-list-all-json` ouptut
- The `netprobe_timeout` setting from the configuration file or command-line was ignored. This has been fixed.
- The TTL or cloaked entries can now be adjusted (thanks to Markus Linnala)
- Cached IP address from DoH servers now expire (thanks to Markus Linnala)
- DNSCrypt certificates can be fetched over Tor and SOCKS proxies
- Retries over TCP are faster
- Improved logging (thanks to Alison Winters)
- Ignore non-TXT records in certificate responses (thanks to Vladimir Bauer)
- A lot of internal cleanups, thanks to Markus Linnala
### Added
- `publicarray-au` resolver Australia (DNSSEC/OpenNIC/Non-logging/Uncensored- hosted on vultr.com maintained by publicarray- https://dns.seby.io).
- `publicarray-au2` resolver Australia (DNSSEC/OpenNIC/Non-logging/Uncensored- hosted on ovh.com.au maintained by publicarray- https://dns.seby.io).
- Optimized relays.
## 2.0.29-beta.3
### Upstream
- Support for Anonymized DNSCrypt has been added.
- Latency with large responses has actually been reduced.
- DNSCrypt certificates can now be retrieved over Tor, proxies, and DNS relays.
- Improved server error reporting (thanks to Alison Winters)
- Quite a lot of internal improvements and bug fixes have been made, thanks to Markus Linnala.
- Improved logging
- Added a workaround for DNS servers using a non-standard provider name.
### Added
- `anonymized_dns` feature (each resolver has 2 relays assigned).
- `scaleway-fr` resolver (DNSSEC/Non-logging/Uncensored- Maintained by Frank Denis- https://fr.dnscrypt.info).
## 2.0.28
### Upstream
- Invalid server entries are now skipped instead of preventing a source from being used. Thanks to Alison Winters for the contribution!
- Truncated responses are immediately retried over TCP instead of waiting for the client to retry. This reduces the latency for large responses.
- Responses sent to the local network are assumed to support at least 1252 bytes packets, and use optional information from EDNS up to 4096 bytes. This also reduces latency.
- Logging improvements: servers are not logged for cached, synthetic and cloaked responses. And the forwarder is logged instead of the regular server for forwarded responses.
## 2.0.27
### Upstream
- The X25519 implementation was changed from using the Go standard implementation to using Cloudflare's CIRCL library. Unfortunately, CIRCL appears to be broken on big-endian systems. That change has been reverted.
- All the dependencies have been updated.
### Changed
- New project mantainer, @quindecim :)
### v2.8.7 (@bluemeda)
- Changed path of configuration file [dnscrypt.toml] from /system/etc/ to /data/media/0/ [or /sdcard]
- Updated binary & configuration files to 2.0.25
- Removed automatic redirection of dns-request and let dnscrypt-proxy do its job only.
### v2.8.5 (@bluemeda)
- Fix #40
### v2.8.4 (@bluemeda)
- Fix failed to copy or backup config file
### v2.8.3 (@bluemeda)
- Fix permission issue
- Add option to replace or backup-restore config file
### v2.8.2 (@bluemeda)
- Fix "binary file is missing"
### v2.8.7 (@bluemeda)
- Update Magisk 18100 requirements
### v2.8.0 (@bluemeda)
- Update binary files 2.0.22
### v2.7.0 (@bluemeda)
- Update binary files 2.0.21
### v2.6.0 (@bluemeda)
- Update binary files to 2.0.19
### v2.5.0 (@bluemeda)
- Update binary files to 2.0.16
- add exception for cloudflare fallback resolver.
### v2.4.0 (@bluemeda)
- Update binary files to 2.0.14
### v2.3.0 (@bluemeda)
- Update binary files to 2.0.10
- Add option to choose auto redirect DNS or manually set with 3rd-party app.
### v2.2.0 (@bluemeda)
- Update binary files to 2.0.8
### v2.1.3 (@bluemeda)
- If you have previous version, please uninstall it first then reinstall it again or you can change listen port manually in dnscrypt-proxy.toml file.
- Fix Tethering Client cannot Resolve DNSCrypt
- Fix Chromecast devices not showing jedisct1/dnscrypt-proxy#226
- Add binary files for x86 and x86_64 (test)
### v2.1.2 (@bluemeda)
- Bug Fixes
### v2.1.1 (@bluemeda)
- Bug fixes
### v2.1 (@bluemeda)
- Bug fixes
### v2.0 (@bluemeda)
- Resolve download.dnscrypt.info first before executing iptable
- Don't override dnscrypt-proxy.toml if exist
- Update binary files to v2.0.6
### v1.1 (@bluemeda)
- Change listen port to 5353 (avoid conflict while tethering)
### v1.0 (@bluemeda)
- Initial release
- dnscrypt-proxy v2.0.5