Dimonius

[Dimonius55]

Thanks for taking the time to report a bug! Before filing, please note:### Summary

The source archives for release 2.1.6 appear to be corrupted or incorrectly generated.

Both “Source code (tar.gz)” and “Source code (zip)” contain only the .ci/ directory and do not include the actual project source code. This makes it impossible to build dnscrypt-proxy 2.1.6 in any packaging system (OpenWrt, Gentoo, FreeBSD ports, Nix, etc.).

The correct source tree does exist in git at commit 6319120c, but the release archives do not match it.

---

Affected files

The following archives are broken:

• Source code (tar.gz)
• Source code (zip)
• https://github.com/DNSCrypt/dnscrypt-proxy/archive/refs/tags/2.1.6.tar.gz
• https://github.com/DNSCrypt/dnscrypt-proxy/archive/refs/tags/2.1.6.zip

All of them contain only:

Need help or have a question? The issue tracker is for confirmed, reproducible bugs only. For installation help, configuration help, troubleshooting, or general questions, please read the documentation first. If you still need assistance, use our Q&A Discussions instead - you'll likely get a faster response there.

---

Before submitting

Please make sure:

• You've read the documentation and this is not answered there already
• You're running the latest version of dnscrypt-proxy (precompiled binaries from this repository)
• The software is correctly installed and configured
• You can reliably reproduce the issue

If the bug requires specific steps to reproduce, please include detailed instructions that would work on a fresh install of macOS, Windows, OpenBSD, or Ubuntu Linux.

Not sure if it's a bug? Start a discussion first - we're happy to help figure it out.

---

Diagnostic output

Please run these commands and paste the output:

./dnscrypt-proxy -version
./dnscrypt-proxy -check
./dnscrypt-proxy -resolve example.com

• I read the documentation and this is not answered there
• Initially raised as discussion #...

What's happening?

When does this occur?

Where does it happen?

How do we replicate the issue?

Expected behavior

Additional context

No Go sources are present.

---

Expected contents

The archive should contain a directory:

with the full source tree, including:

• go.mod
• go.sum
• vendor/
• dnscrypt-proxy/ (Go sources)
• utils/
• contrib/
• ChangeLog
• README.md
• etc.

This structure does exist in git at commit 6319120c.

---

Actual contents

The release archives contain only:

No Go modules, no vendor tree, no source code.

---

Steps to reproduce

1. Download the release archive:

2. Extract it:

3. Observe that the archive contains only .ci/.

---

Impact

This issue breaks packaging and distribution systems that rely on source archives:

• OpenWrt
• Gentoo
• FreeBSD ports
• NixOS
• Linux distributions using automated source fetchers

All of them fail because the release archive does not contain the actual source code.

---

Additional notes

The git commit 6319120c contains the correct source tree.
It appears that GitHub Actions or the release process generated the source archives incorrectly.

---

Request

Please regenerate the release archives for 2.1.6 so that they contain the full source tree.

Thank you!

[jedisct1]

$ curl -L https://github.com/DNSCrypt/dnscrypt-proxy/archive/refs/tags/2.1.6.tar.gz|tar tzvf - |fgrep .go|head

-rw-rw-r--  0 root   root     4355 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/common.go
-rw-rw-r--  0 root   root    35727 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/config.go
-rw-rw-r--  0 root   root     4497 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/crypto.go
-rw-rw-r--  0 root   root     5910 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/dnscrypt_certs.go
-rw-rw-r--  0 root   root    12508 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/dnsutils.go
-rw-rw-r--  0 root   root     1462 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/estimators.go
-rw-rw-r--  0 root   root     1329 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/fuzzing_test.go
-rw-rw-r--  0 root   root     3466 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/local-doh.go
-rw-rw-r--  0 root   root      949 Jan 10  2025 dnscrypt-proxy-2.1.6/dnscrypt-proxy/logger.go
...

Everything is here. Maybe your download was incomplete?

Also, the current version is 2.1.15.

[welwood08]

To add to that, the Source code (tar.gz) and Source code (zip) release files are generated automatically by GitHub and there is no way to provide "regenerated" versions at those URLs (for all I know, GitHub could easily generate them on demand directly from the source tree). As another data point, I checked both of the indicated files in 2.1.6 and they do indeed contain the expected files.

[Dimonius55]

Hello. I am building dnscrypt-proxy v2 as a standalone package for OpenWrt using the standard golang-package.mk build system. My goal is to produce a minimal binary for embedded devices with very limited flash storage (8–16 MB). I am using your source tree in the following structure: dnscrypt-proxy-2.1.6/ go.mod go.sum dnscrypt-proxy/ vendor/ Below is the exact OpenWrt Makefile I use to build the package: ```make include $(TOPDIR)/rules.mk PKG_NAME:=dnscrypt-proxy-go PKG_VERSION:=2.1.6 PKG_RELEASE:=1 PKG_SOURCE:=dnscrypt-proxy-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=file://$(TOPDIR)/dl PKG_SOURCE_SUBDIR:=dnscrypt-proxy-$(PKG_VERSION) PKG_SOURCE_VERSION:=$(PKG_VERSION) PKG_HASH:=SKIP PKG_BUILD_DIR:=$(BUILD_DIR)/dnscrypt-proxy-$(PKG_VERSION) PKG_LICENSE:=ISC PKG_LICENSE_FILES:=LICENSE PKG_BUILD_DEPENDS:=golang/host include $(TOPDIR)/feeds/packages/lang/golang/golang-package.mk include $(INCLUDE_DIR)/package.mk GO_PKG:=. GO_PKG_BUILD_PKG:=./dnscrypt-proxy GO_PKG_TAGS:=no_doh no_dot no_quic no_dnssec no_ipv6 no_systemd no_android no_windows no_pprof no_fuzz define Package/dnscrypt-proxy-go SECTION:=net CATEGORY:=Network TITLE:=DNSCrypt Proxy v2 (Go) DEPENDS:=$(GO_ARCH_DEPENDS) +ca-bundle endef define Package/dnscrypt-proxy-go/install $(INSTALL_DIR) $(1)/usr/sbin $(INSTALL_BIN) $(GO_PKG_BUILD_BIN_DIR)/dnscrypt-proxy $(1)/usr/sbin/ endef $(eval $(call GoPackage,dnscrypt-proxy-go)) $(eval $(call BuildPackage,dnscrypt-proxy-go)) ``` I would like to clarify a few points to ensure I am building dnscrypt-proxy correctly: 1. Is the top-level directory (where go.mod is located) the correct Go module root for building dnscrypt-proxy? 2. Is "./dnscrypt-proxy" the correct and intended path to the main package containing main.go? 3. Are the following build tags valid and safe for producing a minimal binary? no_doh no_dot no_quic no_dnssec no_ipv6 no_systemd no_android no_windows no_pprof no_fuzz If not, which tags should be used for a minimal build? 4. Do you have any recommendations for building a minimal dnscrypt-proxy binary for OpenWrt or other embedded Linux systems? My goal is to produce the smallest possible dnscrypt-proxy binary without unnecessary subsystems, while following the correct module structure and your intended build process. Thank you.

[jedisct1]

Hello @Dimonius55,

Answering your questions:

1. Module root: Yes. The go.mod file is at the repository root (not inside dnscrypt-proxy/), so `.` is correct as the Go module root.

2. Build package path: Yes, `./dnscrypt-proxy` is the correct path. It contains main.go which is the entry point.

3. Build tags — those do not exist. I checked the entire codebase: dnscrypt-proxy does not use any of the tags you listed (no_doh, no_dot, no_quic, no_dnssec, no_ipv6, no_systemd, etc.). The features are all compiled in unconditionally. The only build tags in the codebase are for platform differentiation (linux, android, unix, windows, freebsd, darwin, openbsd) and fuzzing (gofuzzbeta). Using non-existent tags has no effect — the binary will include all features regardless.

If you want a smaller binary on OpenWrt, the effective approaches are:

• `-ldflags="-s -w"` to strip debug info and symbol tables
• `-trimpath` to remove file system paths
• Ensure LTO (link-time optimization) is disabled in the OpenWrt Go toolchain, as it increases binary size significantly
• The systemd service files are only needed at runtime, not at build time, so excluding them does not reduce the binary

4. No special instructions beyond the above. A standard `go build -ldflags="-s -w" ./dnscrypt-proxy` from the repository root should produce the smallest practical binary for embedded systems.

Note: you appear to be building 2.1.6, but the current version is 2.1.15. If you are packaging for a distribution, you may want to check if 2.1.15 or later has changes that affect your build.