From: g4s8 <g4s8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: dnscrypt-proxy: update to 2.1.5.
Date: Thu, 24 Aug 2023 20:28:03 +0200 [thread overview]
Message-ID: <20230824182803.9Sr69o8xr3aus8DtSf-PhAnweNtrePCb7Zj_eS1RLtg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45740@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
There's a closed pull request on the void-packages repository
dnscrypt-proxy: update to 2.1.5.
https://github.com/void-linux/void-packages/pull/45740
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- i686
- aarch64
- armv7l
The new version 2.1.5 fixes go1.21.0 version support, see [changelog](https://github.com/DNSCrypt/dnscrypt-proxy/blob/master/ChangeLog):
# Version 2.1.5
- dnscrypt-proxy can be compiled with Go 1.21.0+
- Responses to blocked queries now include extended error codes
- Reliability of connections using HTTP/3 has been improved
- New configuration directive: `tls_key_log_file`. When defined, this
is the path to a file where TLS secret keys will be written to, so
that DoH traffic can be locally inspected.
prev parent reply other threads:[~2023-08-24 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 12:10 [PR PATCH] " g4s8
2023-08-24 12:13 ` g4s8
2023-08-24 14:27 ` [PR PATCH] [Updated] " g4s8
2023-08-24 16:30 ` cinerea0
2023-08-24 18:28 ` g4s8 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230824182803.9Sr69o8xr3aus8DtSf-PhAnweNtrePCb7Zj_eS1RLtg@z \
--to=g4s8@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).