Your message dated Mon, 01 Aug 2005 01:17:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#318978: fixed in shorewall 2.4.1-3
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Jul 2005 23:44:45 +0000
>From [EMAIL PROTECTED] Mon Jul 18 16:44:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from host-12-107-230-171.dtccom.net
(glaurung.internal.golden-gryphon.com) [12.107.230.171]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1DufHx-0004RA-00; Mon, 18 Jul 2005 16:44:45 -0700
Received: from glaurung.internal.golden-gryphon.com ([EMAIL PROTECTED]
[127.0.0.1])
by glaurung.internal.golden-gryphon.com (8.13.4/8.13.4/Debian-3) with
ESMTP id j6INbLXf002315
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Mon, 18 Jul 2005 18:37:21 -0500
Received: (from [EMAIL PROTECTED])
by glaurung.internal.golden-gryphon.com (8.13.4/8.13.4/Submit) id
j6INbL3n002314;
Mon, 18 Jul 2005 18:37:21 -0500
Message-Id: <[EMAIL PROTECTED]>
X-Authentication-Warning: glaurung.internal.golden-gryphon.com: srivasta set
sender to [EMAIL PROTECTED] using -f
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Manoj Srivastava <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Shorewall upgrade question asked prematurely,
there is no way to answer the question when asked
Reply-To: Manoj Srivastava <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.15
Date: Mon, 18 Jul 2005 18:37:21 -0500
X-CRM114-Score: -20.354
X-CRM114-Status: Good ( pR: -20.354 )
X-SA-Orig: -5.899, -20.354
X-Spam-Value: -11.4742222222222
X-Grey: White
X-SA-Rep: -11.4742222222222 ALL_TRUSTED,BAYES_00
X-Scanned-By: MIMEDefang version 2.51 (www . roaringpenguin . com / mimedefang)
on 192.168.1.10
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: shorewall
Version: 2.4.1-2
Severity: normal
Hi,
On upgrade, shorewall asks the scary looking question:
"Did you check your configuration and do you want to restart
Shorewall right now?"
Followed by:
======================================================================
This is a major release of Shorewall that introduces some changes in
the configuration files. You have to check carefully your
configuration before restarting your firewall to avoid failures and
network blackout. The changes are listed in
/usr/share/doc/shorewall/releasenotes.txt.gz.
======================================================================
Except, of course, they are not yet: the file there is the old
file, since the package has not been unpacked. If the user is not
paying attention, they can read the file, check their configuration
find that is is fine, upgrade, and then procxeed to have holes in the
firewall or blackouts.
There is no information yet as to what changes are going to take
place, and thus this question *MUS* be asked in the postinst, and
_NOT_ in the .config.
I have left the severity at normal, feel free to upgrade severity
to important.
manoj
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.2-skas3-v9-pre4
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages shorewall depends on:
ii debconf 1.4.52 Debian configuration management sy
ii iproute 20041019-3 Professional tools to control the
ii iptables 1.3.1-2 Linux kernel 2.4+ iptables adminis
Versions of packages shorewall recommends:
ii wget 1.10-3+1.10.1beta1 retrieves files from the web
-- debconf information:
* shorewall/upgrade_20_22: true
shorewall/warnrfc1918:
shorewall/dont_restart:
* shorewall/upgrade_14_20: true
shorewall/upgrade_to_14:
shorewall/major_release:
---------------------------------------
Received: (at 318978-close) by bugs.debian.org; 1 Aug 2005 08:35:08 +0000
>From [EMAIL PROTECTED] Mon Aug 01 01:35:08 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1DzVTu-0002YM-00; Mon, 01 Aug 2005 01:17:06 -0700
From: Lorenzo Martignoni <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#318978: fixed in shorewall 2.4.1-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 01 Aug 2005 01:17:06 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Source: shorewall
Source-Version: 2.4.1-3
We believe that the bug you reported is fixed in the latest version of
shorewall, which is due to be installed in the Debian FTP archive:
shorewall_2.4.1-3.diff.gz
to pool/main/s/shorewall/shorewall_2.4.1-3.diff.gz
shorewall_2.4.1-3.dsc
to pool/main/s/shorewall/shorewall_2.4.1-3.dsc
shorewall_2.4.1-3_all.deb
to pool/main/s/shorewall/shorewall_2.4.1-3_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lorenzo Martignoni <[EMAIL PROTECTED]> (supplier of updated shorewall package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 1 Aug 2005 09:45:53 +0200
Source: shorewall
Binary: shorewall
Architecture: source all
Version: 2.4.1-3
Distribution: unstable
Urgency: low
Maintainer: Lorenzo Martignoni <[EMAIL PROTECTED]>
Changed-By: Lorenzo Martignoni <[EMAIL PROTECTED]>
Description:
shorewall - Shoreline Firewall (Shorewall)
Closes: 318978 320732
Changes:
shorewall (2.4.1-3) unstable; urgency=low
.
* Fixed a typo in /etc/defaults/shorewall (Closes: #320732).
* Postponed the prompt to warn users about possible changes in
configuration files from configure to postinst script because during
configure the file /usr/share/doc/shorewall/releasenotes.txt.gz is not
yet updated and users would read previous version releasenotes, thus
they couldn't notice potential configuration changes that could broke
their network configuration (Closes: #318978).
Files:
0aa1983e3ae4309e492e22f9f48b5345 656 net optional shorewall_2.4.1-3.dsc
ac7e0b629ae43cb050a20fc53c743865 40079 net optional shorewall_2.4.1-3.diff.gz
050dd64d5594539bd35c26898d7f3b0a 158122 net optional shorewall_2.4.1-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC7dXnbFctcIsUOXURAhpVAJ9TGqLBfxNOQIWdIAODws1FP35NSACglkgb
pnKPXWIz99WxFsTnt4InrxY=
=QZ3Z
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
