Package: dnssec-trigger Version: 0.13-1 Severity: grave Installing the dnssec-trigger package causes the daemon to fail to start. Running it by hand shows why:
genre ok % dnssec-triggerd Dec 22 02:47:20 dnssec-triggerd[357453] error: could not set SSL_OP_NO_SSLv2 crypto error:00000000:lib(0):func(0):reason(0) Dec 22 02:47:20 dnssec-triggerd[357453] error: cannot setup SSL context Dec 22 02:47:20 dnssec-triggerd[357453] fatal error: could not init server I've seen this on two separate sid systems today. Downgrading fixes the problem. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dnssec-trigger depends on: ii gir1.2-networkmanager-1.0 1.4.4-1 ii init-system-helpers 1.46 ii libc6 2.24-8 ii libgdk-pixbuf2.0-0 2.36.1-1 ii libglib2.0-0 2.50.2-2 ii libgtk2.0-0 2.24.31-1 ii libldns2 1.7.0-1 ii libssl1.1 1.1.0c-2 ii python 2.7.13-1 ii python-gi 3.22.0-2 ii python-lockfile 1:0.12.2-2 ii unbound 1.6.0-2 dnssec-trigger recommends no packages. dnssec-trigger suggests no packages. -- no debconf information -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: https://keybase.io/bk2204
signature.asc
Description: PGP signature
