Package: unbound Version: 1.9.0-2+deb10u1 Severity: important Tags: upstream patch
Dear Maintainer, Unbound fails to answer TCP queries when it's per thread limit is reached. The limit however is being reached too fast because an error introduced in 1.9.0 in some cases wrongly disables the TCP idle-timeout on a socket. There has been an upstream discussion and fix here: - https://nlnetlabs.nl/pipermail/unbound-users/2019-October/011858.html - https://github.com/NLnetLabs/unbound/pull/122 -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-0.bpo.2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unbound depends on: ii adduser 3.118 ii dns-root-data 2019031302 ii libc6 2.28-10 ii libevent-2.1-6 2.1.8-stable-4 ii libfstrm0 0.4.0-1 ii libprotobuf-c1 1.3.1-1+b1 ii libpython3.7 3.7.3-2 ii libssl1.1 1.1.1d-0+deb10u2 ii libsystemd0 241-7~deb10u2 ii lsb-base 10.2019051400 ii openssl 1.1.1d-0+deb10u2 ii unbound-anchor 1.9.0-2+deb10u1 unbound recommends no packages. Versions of packages unbound suggests: ii apparmor 2.13.2-10 -- Configuration Files: /etc/unbound/unbound.conf changed [not included] -- no debconf information
