Your message dated Wed, 12 Dec 2012 08:48:23 +0000
with message-id <[email protected]>
and subject line Bug#695677: fixed in ferm 2.1-4
has caused the Debian Bug report #695677,
regarding domain within a function produces syntax error (wheezy regression)
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 [email protected]
immediately.)


-- 
695677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695677
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ferm
Version: 2.1-3
Severity: important
Tags: fixed-upstream

Hi,

ferm 2.1 and onwards rejects the following stanza as invalid syntax
(missing brace):

    @def &SERVICE($proto, $port) = {
           domain (ip ip6) chain INPUT {
                   proto $proto dport $port ACCEPT;
           }
    }
    &SERVICE(tcp, smtp);

The syntax above is perfectly fine according to the DSL specification
and was accepted by ferm 2.0.7. I know of multiple large installations
that use squeeze, ferm and that feature heavily and the wheezy upgrade
is going to break the firewall set for them (hence the severity).

I've found and fixed the bug and my patch has been merged into
upstream's git as commit 392e58, to be included in 2.1.2.

The patch basically a one-liner that can be cleanly applied to 2.1. I
think it warrants an upload and freeze exception, according to the
current freeze rules.

Thanks,
Faidon

--- End Message ---
--- Begin Message ---
Source: ferm
Source-Version: 2.1-4

We believe that the bug you reported is fixed in the latest version of
ferm, which is due to be installed in the Debian FTP archive.

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.
Alexander Wirt <[email protected]> (supplier of updated ferm 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.8
Date: Tue, 11 Dec 2012 22:59:18 +0100
Source: ferm
Binary: ferm
Architecture: source all
Version: 2.1-4
Distribution: unstable
Urgency: low
Maintainer: Alexander Wirt <[email protected]>
Changed-By: Alexander Wirt <[email protected]>
Description: 
 ferm       - maintain and setup complicated firewall rules
Closes: 694334 695677
Changes: 
 ferm (2.1-4) unstable; urgency=low
 .
   * [4ede608] Backport a patch that fixes a regression in functions containing
     ip and ip6 domains
     (Closes: #695677)
   * [22d4a48] don't modify permissions on /etc/ferm during upgrade
     (Closes: #694334)
Checksums-Sha1: 
 c64c91e2b51ca896e8f202b92cab987b60bc9843 1025 ferm_2.1-4.dsc
 03b76672a6e104fcf13d2cf87f9b802c13bced3c 15577 ferm_2.1-4.diff.gz
 443971601a790e78dfc2fb70fab901fb5ae8abe4 111312 ferm_2.1-4_all.deb
Checksums-Sha256: 
 1fcafb4a262cc56d90885bb92230053201fdfe87aedad31bd3e4559c7b80c7c2 1025 
ferm_2.1-4.dsc
 a2dff764a978c535ba0a4c73dece68b18c152b19d36b4d24827c469a9572451a 15577 
ferm_2.1-4.diff.gz
 9a6c8cfb89375c4129a6eaed08484743c755c2bbd926f817e38b92023e10416e 111312 
ferm_2.1-4_all.deb
Files: 
 b387a70a4daa626af239c99cede70326 1025 net optional ferm_2.1-4.dsc
 323ae73acfa3b7bfe4c5c18dbe7d5172 15577 net optional ferm_2.1-4.diff.gz
 5aea968231d52095b3223ac31f13a0de 111312 net optional ferm_2.1-4_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlDIO7AACgkQ01u8mbx9AgqjrQCgxAWq4Wg8PolTSVfFN4gbWrk9
eBgAoM2KxX26KiSdSGQGSstHTK0JFUSI
=AQIx
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to