Package: hash-slinger Version: 2.7-1~bpo8+1 Severity: normal Hi,
the SNI functionality in the tlsa tool requires a python-m2crypto version that is more recent than the version in jessie - the testing/unstable version pf python-m2crypto works. This is especially problematic for the hash-slinger version in backports (with python-m2crypto from jessie): % tlsa --create publish.willi.space Warning: initial query using resolver config file was not secure (try option --resolvconf=""). Unable to resolve publish.willi.space.: Unsuccessful DNS lookup or no data returned for rrtype AAAA (28). Could not set SNI (old M2Crypto version?) Got a certificate with Subject: /CN=wserver.wm1.at _443._tcp.publish.willi.space. IN TLSA 3 0 1 021a934d464223122257b4bb726d4a7c6eb14dd68971334e04e62ecd8f3e93a6 So I uploaded a backport of python-m2crypto that is currently sitting in backports-NEW. It would be great if you could fix the dependency in unstable and jessie-backports (the latter once the backport has been accepted). thanks Willi -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hash-slinger depends on: ii ca-certificates 20141019+deb8u1 ii dns-root-data 2014060201+2 ii libpython2.7-stdlib [python-argparse] 2.7.9-2 ii openssh-client 1:6.7p1-5+deb8u3 ii python 2.7.9-1 ii python-dnspython 1.12.0-1 ii python-gnupg 0.3.6-1 ii python-ipaddr 2.1.11-2 ii python-m2crypto 0.21.1-3 ii python-unbound 1.5.9-1~bpo8+1 hash-slinger recommends no packages. hash-slinger suggests no packages. -- no debconf information
