arno-iptables-firewall (2.1.2-1) unstable; urgency=medium

    Upstream renamed the configuration variables
    - DENY_TCP_OUTPUT
    - DENY_UDP_OUTPUT
    - DENY_IP_OUTPUT
    - HOST_DENY_TCP_OUTPUT
    - HOST_DENY_UDP_OUTPUT
    - HOST_DENY_IP_OUTPUT
    to
    - INET_OUTPUT_DENY_TCP
    - INET_OUTPUT_DENY_UDP
    - INET_OUTPUT_DENY_IP
    - INET_OUTPUT_HOST_DENY_TCP
    - INET_OUTPUT_HOST_DENY_UDP
    - INET_OUTPUT_HOST_DENY_IP
    respectively. You may want to review your configuration files and adapt
    these if needed.

 -- Sven Geuer <debmaint@g-e-u-e-r.de>  Tue, 21 May 2024 16:50:55 +0200

arno-iptables-firewall (2.1.0-1) unstable; urgency=medium
  
    Up to now background jobs of certain plugins have been run through cron.
    With this release upstream introduces a job manager daemon executing
    the background jobs installed by the respective plugins.

 -- Sven Geuer <debmaint@g-e-u-e-r.de>  Wed, 22 Jan 2020 20:06:21 +0100

arno-iptables-firewall (2.0.1.b-1) experimental; urgency=low

    The package now supports a conf.d-style configuration option that
    makes it possible to tweak the configuration without editing the default
    configuration files. Consequently, the Debconf-based configuration settings
    (if enabled) are no longer written into a custom 'debconf.cfg', but use
    this mechanism also. Additional configuration snippets can be placed into
    /etc/arno-iptables-filewall/conf.d. All files with extension '.conf' will
    be sourced after the main configuration file and either overwrite or
    extend the default.

 -- Michael Hanke <mih@debian.org>  Tue, 10 Apr 2012 10:58:18 +0200

arno-iptables-firewall (1.9.2.a-1) unstable; urgency=low

    With this release the syntax of the config file is slightly changed. From
    now on the '#' (hash-character) is used as the new separator for interface
    restrictions (i.e. eth0#....).

 -- Michael Hanke <michael.hanke@gmail.com>  Tue, 09 Jun 2009 10:12:23 +0200

arno-iptables-firewall (1.9.0.a-1) unstable; urgency=low

    The syntax and layout of the configuration file has been changed. Several
    variable names have been modified, but the most notable difference is the
    switch from ':' to '~' as port separator string. Although most
    installations that exclusively use the debconf-managed configuration
    settings should also work with this version, it is nevertheless recommend
    to verify the firewall setup before reenabling the firewall after
    upgrading. more information is available in
    /usr/share/doc/arno-iptables-firewall/README.gz
    The 1.9 branch now uses a leightweight init.d script without a verbose
    status dump during startup. The 'old' status report is available when
    manually starting the firewall using /usr/sbin/arno-iptables-firewall.
    Additionally, this script, as well as the init.d scripti, provides a details
    iptables configuration dump via the 'status' command.
    A default rsyslog configuration (and corresponding logrotate setup) for
    firewall-related messages is has been added. Such messages will now be
    logged into /var/log/arno-iptables-firewall.

 -- Michael Hanke <michael.hanke@gmail.com>  Fri, 20 Feb 2009 07:31:15 +0100

arno-iptables-firewall (1.8.8.l-1) unstable; urgency=low

    The location of the firewall plugins has changed. The plugins itself are
    now placed in /usr/share/arno-iptables-firewall/plugins, while their
    configuration files remain in /etc/arno-iptables-firewall/plugins.
    Unmodified plugins are silently moved on package upgrade. If any of the
    plugins were modified, the modified plugin is preserved in
    /etc/arno-iptables-firewall/plugins (with a '.dpkg-old' suffix). However,
    only plugins in the new location will be used by the firewall and custom
    modifications have to be updated manually.

 -- Michael Hanke <michael.hanke@gmail.com>  Fri, 25 Jan 2008 11:20:04 +0100

arno-iptables-firewall (1.8.8-1) unstable; urgency=low

    The location of the config files has been changed. All files are now 
    located in /etc/arno-iptables-firewall/. Config files of previous package
    versions are automatically moved into the new location and any
    customizations will be preserved. This includes MAC filter lists and host
    blacklists as well as custom iptables rules.

 -- Michael Hanke <michael.hanke@gmail.com>  Thu,  5 Oct 2006 16:07:34 +0200
