vasek00 Posted November 7, 2019 Share Posted November 7, 2019 Возможно ли поднять Dnscrypt-proxy c текущего 2.0.27 до 2.0.31 Скрытый текст 2.0.31 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. 2.0.30 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! 2.0.29 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 2.0.29-beta.3 Improved logging Added a workaround for DNS servers using a non-standard provider name. 2.0.29-beta.2 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. 2.0.29-beta.1 Preliminary support for anonymized DNS is here! 2.0.28 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. 1 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.