Package: dnscrypt-proxy Version: 2.0.19+ds1-2+b11 Severity: important Dear Maintainer,
The default config file (/etc/dnscrypt-proxy/dnscrypt-proxy.toml) says "Empty listen_addresses to use systemd socket activation" which implies that systemd socket activation will not occur if the listen_addresses field is not blank. However, if I specify a listen address (e.g. listen_addresses = ['127.0.0.1:5353']) and restart (systemctl restart dnscrypt-proxy.service), dnscrypt-proxy is listening on both the address I specified and the address specified in /lib/systemd/system/dnscrypt-proxy.socket. I get the following (I get the same after a reboot): # netstat -anp | grep 53 tcp 0 0 127.0.0.1:5353 0.0.0.0:* LISTEN 7060/dnscrypt-proxy tcp 0 0 127.0.2.1:53 0.0.0.0:* LISTEN 1/init udp 0 0 127.0.2.1:53 0.0.0.0:* 1/init udp 0 0 127.0.0.1:5353 0.0.0.0:* 7060/dnscrypt-proxy This is a problem for things like Pihole, where pihole-FTL needs to listen on port 53 and forward requests to dnscrypt-proxy on another port. Please reconfigure so that systemd sockets are not used if a listen_address is specified in /etc/dnscrypt-proxy/dnscrypt-proxy.toml. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dnscrypt-proxy depends on: ii adduser 3.118 ii libc6 2.28-10 ii lsb-base 10.2019051400 dnscrypt-proxy recommends no packages. Versions of packages dnscrypt-proxy suggests: pn resolvconf <none>
