updating to python2.6.7 in lucid and updating

Bug #788525 reported by Matthias Klose
46
This bug affects 8 people
Affects Status Importance Assigned to Milestone
python2.6 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: python2.6

(started discussion about this kind of update with Barry and Martin)

the python2.6 branch has a lot of bug fixes not present in the lucid python2.6 packages; it would be worth updating the python2.6 package to the 2.6.6 (or the 2.6.7) release. what would need to happen?

 - review changes in the python2.6 branch, these should only be bug fixes (barry - done)
 - backport the py_compileall / pycompile changes, needed for dh_python2 backport (doko)
 - review locally applied bug fixes during the maverick and natty release cycle (doko)

the backport of dh_python2 is tracked in bug #788524

CVE References

Revision history for this message
Barry Warsaw (barry) wrote :

2.6.6 was the last bug fix release for Python 2.6. 2.6.7 (planned for June 3, 2011) and beyond will be security-fix only releases. Yes, there are a *ton* of fixes in 2.6.6. See http://hg.python.org/cpython/file/2d760cb20e1e/Misc/NEWS

I'll review these to find any I think might affect Ubuntu, and check them against any distro patches we might have applied.

Barry Warsaw (barry)
summary: - updating to python2.6.6 or .7 in lucid and updating
+ updating to python2.6.7 in lucid and updating
Revision history for this message
Matthias Klose (doko) wrote :

no, it is not necessary to check the stuff mentioned in #1, because there already is an updated package in oneiric. what needs to be done is to check the changes gone into 2.6.6 and 2.6.7, if these are only regressions fixes, or fixes which do not affect ubuntu (unsupported architectures).

Revision history for this message
Barry Warsaw (barry) wrote :
Download full text (19.8 KiB)

Here are all the changes in upstream Python 2.6.6 and 2.6.7 as defined in the
Misc/News file. I've pulled out all the extraneous information and left just
the issue bullets. Those that could have SRU implications I've marked with
`@@@`.

TL;DR: Here's what Matthias wants to know: "check the upstream changes made
since 2.6.5 and make sure that these are bug and regression fixes only". The
one new feature is issue 5753, but that cannot hurt existing code, since it
won't be written to use the new API, and besides the new API fixes a CVE.

Bottom line: all other changes are bug and regression fixes only.

Details:

- Issue #11662: Make urllib and urllib2 ignore redirections if the
  scheme is not HTTP, HTTPS or FTP (CVE-2011-1521).

- Issue #11442: Add a charset parameter to the Content-type in SimpleHTTPServer
  to avoid XSS attacks.

- Issue #9129: smtpd.py is vulnerable to DoS attacks deriving from missing
  error handling when accepting a new connection.

- Issue #9600: Don't use relative import for _multiprocessing on Windows.

- Issue #8688: Revert regression introduced in 2.6.6rc1 (making Distutils
  recalculate MANIFEST every time).

- Issue #5798: Handle select.poll flag oddities properly on OS X.
  This fixes test_asynchat and test_smtplib failures on OS X.

- Issue #9543: Fix regression in socket.py introduced in Python 2.6.6 rc 1
  in r83624.

- Issue #7567: Don't call `setupterm' twice.

- Issue #9568: Fix test_urllib2_localnet on OS X 10.3.

- Issue #9145: Fix test_coercion failure in refleak runs.

- Issue #8433: Fix test_curses failure caused by newer versions of
  ncurses returning ERR from getmouse() when there are no mouse
  events available.

- Issue #6213: Implement getstate() and setstate() methods of utf-8-sig and
  utf-16 incremental encoders.

@@@ Since the return value of getstate() changed, this could potentially cause
some code to break, but I think that this is such an obscure API, the
likelihood is very low.

- Issue #8271: during the decoding of an invalid UTF-8 byte sequence, only the
  start byte and the continuation byte(s) are now considered invalid, instead
  of the number of bytes specified by the start byte.
  E.g.: '\xf1\x80AB'.decode('utf-8', 'replace') now returns u'\ufffdAB' and
  replaces with U+FFFD only the start byte ('\xf1') and the continuation byte
  ('\x80') even if '\xf1' is the start byte of a 4-bytes sequence.
  Previous versions returned a single u'\ufffd'.

- Issue #9058: Remove assertions about INT_MAX in UnicodeDecodeError.

- Issue #8941: decoding big endian UTF-32 data in UCS-2 builds could crash
  the interpreter with characters outside the Basic Multilingual Plane
  (higher than 0x10000).

- Issue #8627: Remove bogus "Overriding __cmp__ blocks inheritance of
  __hash__ in 3.x" warning. Also fix "XXX undetected error" that
  arises from the "Overriding __eq__ blocks inheritance ..." warning
  when turned into an exception: in this case the exception simply
  gets ignored.

- Issue #4108: In urllib.robotparser, if there are multiple 'User-agent: *'
  entries, consider the first one.

- Issue #9354: Provide getsockopt() in asyncore's file_wrapper.

- In the unicode/str.format(), raise ...

description: updated
Changed in python2.6 (Ubuntu):
status: New → Confirmed
Revision history for this message
Barry Warsaw (barry) wrote :

Matthias, any thoughts on this? Was the information in comment #3 sufficient?

Revision history for this message
Alex Grönholm (agronholm) wrote :

I just got hit by this. Why has this not gone forward since August?

Revision history for this message
Roger Hu (roger-hu) wrote :

Any update on whether Python 2.6.7 will make its way into Ubuntu 10.04? The SSL handshake indefinite timeout bug happens to be a big one on the list to fix. Thanks!

Revision history for this message
dino99 (9d9) wrote :

Support for this version has ended

Changed in python2.6 (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.