<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ports/lang/python25/files, branch 7-eol</title>
<subtitle>FreeBSD ports tree</subtitle>
<id>https://cgit-dev.freebsd.org/ports/atom?h=7-eol</id>
<link rel='self' href='https://cgit-dev.freebsd.org/ports/atom?h=7-eol'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/'/>
<updated>2012-07-16T17:04:29Z</updated>
<entry>
<title>- remove expired ports</title>
<updated>2012-07-16T17:04:29Z</updated>
<author>
<name>Ruslan Makhmatkhanov</name>
<email>rm@FreeBSD.org</email>
</author>
<published>2012-07-16T17:04:29Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=473f7fc2dc1cba782abaf6af536acb7a7799336e'/>
<id>urn:sha1:473f7fc2dc1cba782abaf6af536acb7a7799336e</id>
<content type='text'>
  * lang/python24 and lang/python25: unmaintained upstream
  * www/zope and www/zope211: unmaintained upstream (the only
    consumers of python24)
- clean-up python versions &lt; 2.6 from lang/python-doc-html
- clean-up python24/25 from Mk/bsd.ports.mk
- add www/zope213 glue to bsd.python.mk
- clean-up zope versions != 2.13 from bsd.python.mk

Submitted by:	miwi (based on)
Approved by:	portmgr (miwi)
</content>
</entry>
<entry>
<title>- Mark Python as Secure</title>
<updated>2012-02-18T17:53:53Z</updated>
<author>
<name>Martin Wilke</name>
<email>miwi@FreeBSD.org</email>
</author>
<published>2012-02-18T17:53:53Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=c70027929c625a6c7a644180cb76d4bdfcf68a9c'/>
<id>urn:sha1:c70027929c625a6c7a644180cb76d4bdfcf68a9c</id>
<content type='text'>
- Fix DoS via malformed XML-RPC / HTTP POST

Submitted by:	rm@
Reported by:	many
Obtained from:	python hg
Security:	http://www.vuxml.org/freebsd/b4f8be9e-56b2-11e1-9fb7-003067b2972c.html
</content>
</entry>
<entry>
<title>- Fix build on FreeBSD 10</title>
<updated>2011-10-28T10:42:24Z</updated>
<author>
<name>Beat Gaetzi</name>
<email>beat@FreeBSD.org</email>
</author>
<published>2011-10-28T10:42:24Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=5bc148fb49f344096c1b58fc5cdea109d4171688'/>
<id>urn:sha1:5bc148fb49f344096c1b58fc5cdea109d4171688</id>
<content type='text'>
Approved by:	miwi (implicit)
</content>
</entry>
<entry>
<title>Fix fcntl module to accept 'unsigned long' type commands for ioctl(2).</title>
<updated>2010-07-19T21:59:28Z</updated>
<author>
<name>Jung-uk Kim</name>
<email>jkim@FreeBSD.org</email>
</author>
<published>2010-07-19T21:59:28Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=5045cff4a059fb43d185e75ed1258eb9fbe4ca4b'/>
<id>urn:sha1:5045cff4a059fb43d185e75ed1258eb9fbe4ca4b</id>
<content type='text'>
Although POSIX says the type is 'int', all BSD variants (including Mac OS X)
have been using 'unsigned long' type for very long time and its use predates
the standard long enough.  For certain commands (e.g., TIOCSWINSZ, FIONBIO),
the Python value may get sign-extended on 64-bit platforms (by implicit type
promotion) and it causes annoying warnings from kernel such as this:

WARNING pid 24509 (python2.6): ioctl sign-extension ioctl ffffffff8004667e

Approved by:	python (maintainer timeout)
</content>
</entry>
<entry>
<title>- Add support for FreeBSD 9</title>
<updated>2009-11-26T14:04:19Z</updated>
<author>
<name>Martin Wilke</name>
<email>miwi@FreeBSD.org</email>
</author>
<published>2009-11-26T14:04:19Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=e8252e4d6ba57fd86ca89a0bd02cbe8f1251099a'/>
<id>urn:sha1:e8252e4d6ba57fd86ca89a0bd02cbe8f1251099a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove ../ from patch.</title>
<updated>2009-02-27T04:05:33Z</updated>
<author>
<name>Maxim Sobolev</name>
<email>sobomax@FreeBSD.org</email>
</author>
<published>2009-02-27T04:05:33Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=fbf0ee5e6da42985c449e9db91624c7c5e344c58'/>
<id>urn:sha1:fbf0ee5e6da42985c449e9db91624c7c5e344c58</id>
<content type='text'>
Submitted by:	QAT
</content>
</entry>
<entry>
<title>Make sure the singal is delivered to the main thread, where python</title>
<updated>2009-02-27T01:25:32Z</updated>
<author>
<name>Maxim Sobolev</name>
<email>sobomax@FreeBSD.org</email>
</author>
<published>2009-02-27T01:25:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=f4711ece62ae605030165a01431ea6a36f7ea096'/>
<id>urn:sha1:f4711ece62ae605030165a01431ea6a36f7ea096</id>
<content type='text'>
runs its signal handlers, not to a random thread that happens to be
executing at the time when signal arrives. This functionality has been
lost since Python 2.3, possible cause is that the linux implementation
of POSIX threads always delivered signal to the main thread. This
bug results in rather annoying inability to terminate threading script
with ^C for example and there could be other issues as well.

Bump PORTREVISION.

PR:		ports/131080
Submitted by:	Andriy Pylypenko &lt;bamby@sippysoft.com&gt;
Approved by:	MAINTAINER's timeout
</content>
</entry>
<entry>
<title>- Remove 0 byte patches</title>
<updated>2009-02-17T08:29:34Z</updated>
<author>
<name>Martin Wilke</name>
<email>miwi@FreeBSD.org</email>
</author>
<published>2009-02-17T08:29:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=722bccf2f20b9499c7524ee15970ca0c187f1286'/>
<id>urn:sha1:722bccf2f20b9499c7524ee15970ca0c187f1286</id>
<content type='text'>
Reported by:	Gej
</content>
</entry>
<entry>
<title>- Update to python 2.5.4 and python 2.6.1</title>
<updated>2009-02-16T23:32:02Z</updated>
<author>
<name>Martin Wilke</name>
<email>miwi@FreeBSD.org</email>
</author>
<published>2009-02-16T23:32:02Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=c95782ae1ae828e8cc558bd2b4c5c906e8416814'/>
<id>urn:sha1:c95782ae1ae828e8cc558bd2b4c5c906e8416814</id>
<content type='text'>
Reviewed by:	perky | lwhsu
Tested with:	exp-run via pav
</content>
</entry>
<entry>
<title>- Security fixes</title>
<updated>2008-09-08T00:14:06Z</updated>
<author>
<name>Martin Wilke</name>
<email>miwi@FreeBSD.org</email>
</author>
<published>2008-09-08T00:14:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/ports/commit/?id=8a1ff65b9b4abb36af6477b5c168037be07d4f71'/>
<id>urn:sha1:8a1ff65b9b4abb36af6477b5c168037be07d4f71</id>
<content type='text'>
Multiple vulnerabilities:

	1) Various integer overflow errors exist in core modules e.g. stringobject,
	   unicodeobject, bufferobject, longobject, tupleobject, stropmodule, gcmodule, mmapmodule.
	2) An integer overflow in the hashlib module can lead to an unreliable cryptographic digest results.
	3) Integer overflow errors in the processing of unicode strings can be exploited to cause
	   buffer overflows on 32-bit systems.
	4) An integer overflow exists in the PyOS_vsnprintf() function on architectures that do not
	   have a "vsnprintf()" function.
	5) An integer underflow error in the PyOS_vsnprintf() function when passing zero-length strings
	   can lead to memory corruption.

PR:		127172 (based on)
Submitted by:	bf &lt;bf2006a@yahoo.com&gt;
Obtained from:	python svn
Security:	CVE-2008-2315, CVE-2008-2316, CVE-2008-3142, CVE-2008-3144, CVE-2008-3143. (vuxml come later)
</content>
</entry>
</feed>
