Package: python2.7 Version: 2.7.13-2 Severity: normal [stratocaster ~]nm --dynamic /usr/bin/python2.7 | grep md5 00091732 T init_md5 001d6890 T md5_append 001d67d0 T md5_finish 000919f3 T md5_init [stratocaster ~]
This causes trouble when trying to use bindings to a crypto library which also wants to define `md5_init', because they disagree about how the hashing state ought to be arranged: the outcome is a wrong answer on amd64, and a segfault on i386. While it can certainly be argued that neither Python nor the other library has especially good taste in naming, `md5_init' is at least a proper, documented part of the library's public interface, directly relevant to its purpose (and has been since 1999), though the same can't be argued for Python: [stratocaster ~]grep -ri md5 /usr/include/python2.7/ [stratocaster ~] Indeed, it seems that the Python package has leaked its MD5 symbols before: see bug #440272. I'm deploying an awful hack involving `RTLD_DEEPBIND' in the meantime, but it would be nice to get this fixed properly. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 4.9.0-3-amd64 (SMP w/3 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages python2.7 depends on: ii libpython2.7-stdlib 2.7.13-2 ii mime-support 3.60 ii python2.7-minimal 2.7.13-2 python2.7 recommends no packages. Versions of packages python2.7 suggests: ii binutils 2.28-5 ii python2.7-doc 2.7.13-2 -- no debconf information
