Your message dated Tue, 20 Dec 2011 21:23:27 +0100
with message-id <20111220202327.gd24...@ngolde.de>
and subject line Re: Bug#652653: python-virtualenv: insecure /tmp file handling
has caused the Debian Bug report #652653,
regarding python-virtualenv: insecure /tmp file handling
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
652653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-virtualenv
Version: 1.4.9-3
Severity: grave
Tags: patch
Hi,
it was discovered that python-virtualenv is handling /tmp files in an insecure
manner.
The following patch fixed this problem:
https://bitbucket.org/ianb/virtualenv/changeset/8be37c509fe5
A CVE id for this issue has been requested.
Kind regards
Nico
--- End Message ---
--- Begin Message ---
Version: 1.4.9-1
Hi,
* Adam D. Barratt <a...@adam-barratt.org.uk> [2011-12-19 23:35]:
> On Mon, 2011-12-19 at 17:19 +0100, Nico Golde wrote:
> > it was discovered that python-virtualenv is handling /tmp files in an
> > insecure manner.
> > The following patch fixed this problem:
> > https://bitbucket.org/ianb/virtualenv/changeset/8be37c509fe5
>
> I noticed that an upload which appears to fix this issue (although
> without reference the bug number) has appeared in p-u-NEW. Whilst
> that's an admirable turn-around :-) it really should have been discussed
> with the SRMs first, rather than simply uploading (I believe this is
> well documented enough by now - if not, please point out where and how
> we could make it clearer).
>
> Looking at the diff, and the equivalent code in the unstable package,
> there seems to be a missing component - namely, that the directory
> created via mkdtemp() is never cleaned up. Am I missing something, or
> does fixing this issue result in orphaned temporary directories?
I mark this as fixed in 1.4.9-1. It's true that the patch doesn't clean the
directory, but since that is not security related I don't mind. lenny/squeeze
still have the vulnerable code.
Kind regards
Nico
--
Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0AAAA
For security reasons, all text in this mail is double-rot13 encrypted.
pgpnpe72lC19s.pgp
Description: PGP signature
--- End Message ---
_______________________________________________
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
