Bug#690075: marked as done (unblock: dnsmasq/2.63-4)
Your message dated Wed, 6 Feb 2013 17:43:19 +0100
with message-id <20130206164319.GA15758@inutil.org>
and subject line Re: Bug#690075: unblock: dnsmasq/2.63-4
has caused the Debian Bug report #690075,
regarding unblock: dnsmasq/2.63-4
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 owner@bugs.debian.org
immediately.)
--
690075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690075
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: dnsmasq/2.63-4
- From: Moritz Muehlenhoff <jmm@debian.org>
- Date: Tue, 09 Oct 2012 19:51:26 +0200
- Message-id: <20121009175126.5477.63182.reportbug@pisco.westfalen.local>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package dnsmasq
It fixes CVE-2012-3411
unblock dnsmasq/2.63-4
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Wed, Feb 06, 2013 at 12:07:21AM +0100, Michael Stapelberg wrote:
> On Wed, 12 Dec 2012 12:11:12 +0100
> intrigeri <intrigeri@debian.org> wrote:
> > A new upstream release was uploaded to unstable since then, so this
> > unblock request can't be satisfied as is. Please either update or
> > close it.
> Actually, unstable got 2.64-1 _and_ 2.65-1 by now.
>
> Simon: Are these uploads necessary to fix the security issue this
> unblock request talks about (CVE-2012-3411)?
>
> If so, can you please close this unblock request and open a new one?
>
> If not, it would be better to upload new versions to experimental
> during the freeze. Your best option (AFAICT) is to prepare an upload to
> t-p-u now.
That unblock request can be closed, since the required changes are too
intrusive at this point of the release.
The impact of the security issue is low and we won't fix it for Wheezy.
Cheers,
Moritz
--- End Message ---
Reply to: