Your message dated Fri, 26 Nov 2010 14:41:17 +0100
with message-id <4cefb8fd.5020...@debian.org>
and subject line Re: Bug#601690: CVE-2010-3493: smtpd module
has caused the Debian Bug report #601690,
regarding CVE-2010-3493: smtpd module
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.)


-- 
601690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python2.6
Severity: grave
Tags: security
Justification: user security hole

Dear Python maintainers,
please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3493
for details.

A patch is available here:
http://svn.python.org/view/python/branches/release26-maint/Lib/smtpd.py?r1=73770&r2=82406&view=patch

Python 3.1 is already fixed.

Cheers,
        Moritz       


-- System Information:
Debian Release: 5.0.1
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.32-ucs16-amd64
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)



--- End Message ---
--- Begin Message ---
On 04.11.2010 19:07, Moritz Muehlenhoff wrote:
On Mon, Nov 01, 2010 at 02:26:28PM +0100, Matthias Klose wrote:
tag 601690 + moreinfo help
thanks

On 28.10.2010 16:26, Moritz Muehlenhoff wrote:
Package: python2.6
Severity: grave
Tags: security
Justification: user security hole

Dear Python maintainers,
please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3493
for details.

A patch is available here:
http://svn.python.org/view/python/branches/release26-maint/Lib/smtpd.py?r1=73770&r2=82406&view=patch

Python 3.1 is already fixed.

and 2.6.6 too ... at least the svn version you mention.

You're right. Python 2.6 is fixed as well. I must've mixed that up
with Python 2.5, which is still unfixed.

closing.


--- End Message ---

Reply via email to