Bug#692439: marked as done (tomcat6: CVE-2012-2733 CVE-2012-3439)

2012-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Nov 2012 11:52:40 -0500
with message-id 
CANTw=mmwbw-orl0he2o_yqhopnosomzhlaf9aqe5wzgu-dx...@mail.gmail.com
and subject line Re: closing
has caused the Debian Bug report #692439,
regarding tomcat6: CVE-2012-2733 CVE-2012-3439
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.)


-- 
692439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: tomcat6
Severity: grave
Tags: security
Justification: user security hole

Please see http://tomcat.apache.org/security-6.html

Since Wheezy is frozen, please apply isolated security fixes and do not update
to a new upstream release.

BTW, is it really necessary to have both tomcat6 and tomcat7 in Wheezy? 
Shouldn't
tomcat6 be dropped in favour of tomcat7?

Cheers,
Moritz
---End Message---
---BeginMessage---
version: 6.0.35-5+nmu1---End Message---
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#692439: marked as done (tomcat6: CVE-2012-2733 CVE-2012-3439)

2012-11-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 Nov 2012 20:48:41 -0500
with message-id 
CANTw=MMTdWnFvD6vgQ2tN8bDByvg979e5ZZ-nUOi4RfepF=m...@mail.gmail.com
and subject line re: tomcat6: CVE-2012-2733 CVE-2012-3439
has caused the Debian Bug report #692439,
regarding tomcat6: CVE-2012-2733 CVE-2012-3439
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.)


-- 
692439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: tomcat6
Severity: grave
Tags: security
Justification: user security hole

Please see http://tomcat.apache.org/security-6.html

Since Wheezy is frozen, please apply isolated security fixes and do not update
to a new upstream release.

BTW, is it really necessary to have both tomcat6 and tomcat7 in Wheezy? 
Shouldn't
tomcat6 be dropped in favour of tomcat7?

Cheers,
Moritz
---End Message---
---BeginMessage---
version: 6.0.35+nmu1

Hi, I've uploaded an nmu fixing this issue.  Please see attached
patch.  Note I incorrectly entered the tomcat7 bug in the changelog,
which should be corrected in the next upload.

Best wishes,
Mike


tomcat6.patch
Description: Binary data
---End Message---
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for discussions and questions.