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-common
Version: 1.8.4beta1-3.1
Severity: important
Tags: patch
Cron script (/etc/cron.daily/5snort) can't generate a useful report as
it doesn't check the alert (/var/log/snort/alert) file. Here is a small
patch attached for the script.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux ney 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
Locale: LANG=tr_TR, LC_CTYPE=tr_TR
Versions of packages snort-common depends on:
ii adduser 3.47 Add and remove users and groups
ii debconf 1.0.32 Debian configuration management sy
ii snort 1.8.4beta1-3.1 Flexible NIDS (Network Intrusion D
ii snort-rules-default [snor 1.8.4beta1-3.1 Flexible NIDS (Network Intrusion D
ii sysklogd [syslogd] 1.4.1-10 System Logging Daemon
ii sysklogd [system-log-daem 1.4.1-10 System Logging Daemon
--
Baris Metin
http://www.metin.org
--- 5snort 2003-10-09 22:29:46.000000000 +0300
+++ 5snort.new 2003-10-09 22:29:27.000000000 +0300
@@ -12,6 +12,8 @@
SYSLOG_LOGFILE=$SYSLOG_LOGFILE_CUSTOM
fi
+SYSLOG_LOGFILE=$SYSLOG_LOGFILE" /var/log/snort/alert"
+
CONFIG=/etc/snort/snort.debian.conf
. $CONFIG
export DEBIAN_SNORT_STATS_RCPT DEBIAN_SNORT_STATS_TRESHOLD
--- 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
signature.asc
Description: Digital signature
--- End Message ---
