Your message dated Wed, 9 Aug 2006 00:53:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing ancient (tagged woody) bugs
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: snort
Version: N/A; reported 2002-09-20
Severity: normal



-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux homer.infomatrix.internal 2.2.19 2.2.19pre17 #1 Wed Sep 26 
23:33:53 BST 2001 i686
Locale: LANG=en_GB, LC_CTYPE=en_GB

This problem is such that when snort is installed and the debconf
interface asks the user for the relevant configuration details, these
details are written into the /var/cache/debconf/config.dat and
/var/cache/debconf/templates.dat files, but are never written to
/etc/snort/snort.debian.conf file.

This causes the application to start with the default settings of
192.168.0.0/16 for the $HOME_NET variable and to listen on eth0

This has shown itself on several hosts, although all of those were
upgraded from 2.2. I have thus far been unable to test it on a fresh
install.

Installing the unstable package on a Sid machine produced the correct
/etc/snort/snort.debian.conf file which I was able to transfer to the
affected host and use.



--- End Message ---
--- Begin Message ---
Hi,

This bug has been open for quite a long time and it is tagged 'woody'. As the
latest Debian release 3.1 'sarge' has been available since last year and this
bugs do not seem to be present there I'm closing this bug.

Please reopen the bug if you have evidence that this bug is still present in
newer versions of the package. Any additional information would also be
really useful.

Thanks

Javier

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to