[Bug 1734109] Re: Avoid symbol conflicts with `md5_*' symbols in third party extensions

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.3

---------------
python2.7 (2.7.12-1ubuntu0~16.04.3) xenial-proposed; urgency=medium

  * Some performance improvements: LP: #1638695.
    - Build the _math.o object file without -fPIC for static builds.
  * Rename md5_* functions to _Py_md5_*. Closes: #868366. LP: #1734109.
  * Explicitly use the system python for byte compilation in postinst scripts.
    LP: #1682934.
  * Fix issue #22636: Avoid shell injection problems with
    ctypes.util.find_library(). LP: #1512068.

 -- Matthias Klose <doko at ubuntu.com>  Mon, 04 Dec 2017 15:50:18 +0100

** Changed in: python2.7 (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1734109

Title:
  Avoid symbol conflicts with `md5_*' symbols in third party extensions

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Released
Status in python2.7 source package in Zesty:
  Fix Committed
Status in python2.7 source package in Artful:
  Fix Released

Bug description:
  SRU

  We link most extensions as built-ins into the python binary. the md5_*
  symbols cause a conflict with external libs/extensions.  So just use
  the _Py-* namespace for these. See the Debian report for details.

  These are internal functions for the md5 module. Renaming them to the
  _Py_* namespace avoids the conflict.  There should not be any case
  where these are intentionally referenced. At least in the archive
  there are no known references, so the regression potential is limited
  to external binaries, and there it should be minimal to non-existing
  as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1734109/+subscriptions