På tirsdag 21. juli 2026 kl. 17:56, skrev Igor Zornik
<[email protected]>:

> Hello, ports!
> 
> One notable feature new version of DNSCrypt proxy brings is something
> called post-quantum DNSCrypt. It's turned on by default so you don't
> have to do anything to use it. I've been running it on my router for a
> couple of days without any regressions. Another build and quick test
> successfully done on today's amd64 snap.
> 
> I'm also assuming MAINTAINER as that position is now available for
> taking. QP-encoded diff below the changelogs. Someone please commit if
> OK.
> 
> Changelog (2.1.17):
> - Added support for PQDNSCrypt (DNSCrypt 2026), using post-quantum
>   cryptography with compatible DNSCrypt servers to protect query
>   confidentiality against future quantum computers. It is enabled by
>   default and can be disabled with the new 'pqdnscrypt' setting.
> - Key material is now rotated when the local network changes, reducing
>   linkability across network changes.
> - Fixed a cache issue that could corrupt cached responses or cause data
>   races under concurrent use.
> - The 'netprobe_timeout' configuration setting is now honored instead
>   of being silently overridden by its command-line default.
> - Forwarded queries now correctly fall back to TCP after a truncated
>   UDP response, and SOCKS-proxied anonymized DNS exchanges are sent to
>   the relay.
> - HTTP/3 connections now retry after transient failures, and bootstrap
>   resolution succeeds when at least one address was obtained.
> - Cloaking rules that resolve through a rule ending in an IP address
>   are no longer incorrectly rejected as recursive. Actual loops are
>   still rejected.
> - The monitoring dashboard now resolves API paths against the page
>   origin, allowing it to work correctly when hosted under a path.
> 
> Changelog (2.1.18):
> - Forwarding rules now support the '$PROXY:' prefix to send selected
>   plain DNS upstreams over DNS-over-TCP through the proxy configured by
>   the main 'proxy' setting.
> - PQDNSCrypt certificate retrieval is more reliable on paths where
>   fragmented UDP packets are blocked, including when certificates are
>   fetched through Anonymized DNSCrypt relays.
> - Resolver latency measurements no longer include setup or
>   certificate-transfer time, so startup benchmarks and server selection
>   better reflect actual query response time.
> 
> Detailed changelog is available at
> https://github.com/DNSCrypt/dnscrypt-proxy/releases/tag/2.1.17
> and
> https://github.com/DNSCrypt/dnscrypt-proxy/releases/tag/2.1.18
> 


Built/Tested current/amd64 with privsep.

$ cd /usr/ports/net/dnscrypt-proxy/ && patch -l -p0 -E < 
/tmp/dnscrypt-proxy-2.1.18.patch

$ cd /usr/ports/net/dnscrypt-proxy/ && make clean=all clean && make build 
package test ; make port-lib-depends-

  checks:  2009 passed  0 todo  0 failed        (total)
exit status 1
FAIL    github.com/DNSCrypt/dnscrypt-proxy/dnscrypt-proxy       96.476s
--
// Think that is fine? Check had no complaints. No plist changes

// Updated
# TRUSTED_PKG_PATH=/usr/ports/packages/amd64/all/ pkg_add -Dsnap -u 
dnscrypt-proxy
dnscrypt-proxy-2.1.16->2.1.18: ok
--

Ran it for a few hours. No obvious regressions.

Thanks for the update. Hope this helps.
--
yaydn


> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v
> retrieving revision 1.74
> diff -u -p -u -p -r1.74 Makefile
> --- Makefile  6 Jul 2026 09:25:09 -0000       1.74
> +++ Makefile  21 Jul 2026 15:38:47 -0000
> @@ -2,11 +2,13 @@ COMMENT =   flexible DNS proxy with suppor
> 
>  GH_ACCOUNT = DNSCrypt
>  GH_PROJECT = dnscrypt-proxy
> -GH_TAGNAME = 2.1.16
> +GH_TAGNAME = 2.1.18
> 
>  CATEGORIES = net
> 
>  HOMEPAGE =   https://dnscrypt.info/
> +
> +MAINTAINER = Igor Zornik <[email protected]>
> 
>  # ISC
>  PERMIT_PACKAGE =     Yes
> Index: distinfo
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/distinfo,v
> retrieving revision 1.43
> diff -u -p -u -p -r1.43 distinfo
> --- distinfo  6 Jul 2026 09:25:09 -0000       1.43
> +++ distinfo  21 Jul 2026 15:38:47 -0000
> @@ -1,2 +1,2 @@
> -SHA256 (dnscrypt-proxy-2.1.16.tar.gz) = 
> e6WqdtP9xvu2Z2iboT2Kw+Zr4nZVaVqdQS5a1K/jT40=
> -SIZE (dnscrypt-proxy-2.1.16.tar.gz) = 3595664
> +SHA256 (dnscrypt-proxy-2.1.18.tar.gz) = 
> m4ENhiugfDg8wLj59/Hyyo90oC+EnYGMTE03zCGn36Y=
> +SIZE (dnscrypt-proxy-2.1.18.tar.gz) = 3474338
> Index: pkg/DESCR
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/pkg/DESCR,v
> retrieving revision 1.4
> diff -u -p -u -p -r1.4 DESCR
> --- pkg/DESCR 3 Sep 2025 07:57:36 -0000       1.4
> +++ pkg/DESCR 21 Jul 2026 15:38:47 -0000
> @@ -1,9 +1,11 @@
>  dnscrypt-proxy is a flexible DNS proxy, with support for modern
> -encrypted DNS protocols such as DNSCrypt v2, DNS-over-HTTPS, Anonymized
> -DNSCrypt and ODoH (Oblivious DoH), and features:
> +encrypted DNS protocols such as DNSCrypt v2 including Post-Quantum
> +DNSCrypt (DNSCrypt 2026), DNS-over-HTTPS, Anonymized DNSCrypt and ODoH
> +(Oblivious DoH), and features:
> 
>  - DNS traffic encryption and authentication. Supports DNS-over-HTTPS
> -  (DoH) using TLS 1.3 and QUIC, DNSCrypt, Anonymized DNS and ODoH
> +  (DoH) using TLS 1.3 and QUIC, PQDNSCrypt, DNSCrypt, Anonymized DNS and
> +  ODoH
>  - Client IP addresses can be hidden using Tor, SOCKS proxies or
>    Anonymized DNS relays
>  - DNS query monitoring, with separate log files for regular and
> 
>

Reply via email to