Your message dated Tue, 27 Jun 2006 08:53:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323206: psad: iptables method fails for unclear reasons
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)
--- Begin Message ---
Package: psad
Version: 1.4.1-1
Severity: minor
I'm experimenting with the audo-IDS feature, and it does create the new
netfilter chain and does insert a jump rule from the INPUT chain to the
newly created chain. The new rule, however, is inserted at the first
position--not the position I configured for it.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages psad depends on:
ii ipchains 1.3.10-15 Network firewalling for Linux 2.2.
ii iptables 1.3.1-2 Linux kernel 2.4+ iptables adminis
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libcarp-clan-perl 5.3-3 Perl enhancement to Carp error log
ii libdate-calc-perl 5.4-3 Perl library for accessing dates
ii libnetwork-ipv4addr-perl 0.10-1.1 The Net::IPv4Addr perl module API
ii libunix-syslog-perl 0.100-4 Perl interface to the UNIX syslog(
ii perl 5.8.4-8 Larry Wall's Practical Extraction
ii psmisc 21.6-1 Utilities that use the proc filesy
ii sysklogd [syslogd] 1.4.1-17 System Logging Daemon
ii whois 4.7.5 the GNU whois client
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 2006-02-03 at 14:34 +0700, Jeroen Vermeulen wrote:
> On Fri, Feb 03, 2006 at 08:19:43AM +0100, Daniel Gubser wrote:
> > So this is working now for you?
> It is, but I ran into some more problems (reported as two separate
> bug tickets). One of them is #351196; I don't have an acknowledgment
> for the other one yet.
So I guess I can close these to bugs, but feel free to reopen it if I am
wrong.
Daniel
--- End Message ---
