[Logcheck-commits] r1209 - in logcheck/trunk: debian docs

[madduck at users.alioth.debian.org]

Author: madduck
Date: 2006-07-29 15:59:56 +0000 (Sat, 29 Jul 2006)
New Revision: 1209

Modified:
   logcheck/trunk/debian/changelog
   logcheck/trunk/docs/README.logcheck-database
Log:
documentation update by micah anderrson

Modified: logcheck/trunk/debian/changelog
===================================================================
--- logcheck/trunk/debian/changelog	2006-07-29 09:22:54 UTC (rev 1208)
+++ logcheck/trunk/debian/changelog	2006-07-29 15:59:56 UTC (rev 1209)
@@ -1,3 +1,9 @@
+logcheck (1.2.47a~madduck.2) sarge-backports; urgency=low
+
+  * Test release.
+
+ -- martin f. krafft <madduck at debian.org>  Sat, 29 Jul 2006 10:19:08 +0100
+
 logcheck (1.2.48) UNRELEASED; urgency=low
 
   [ maximilian attems ]

Modified: logcheck/trunk/docs/README.logcheck-database
===================================================================
--- logcheck/trunk/docs/README.logcheck-database	2006-07-29 09:22:54 UTC (rev 1208)
+++ logcheck/trunk/docs/README.logcheck-database	2006-07-29 15:59:56 UTC (rev 1209)
@@ -12,12 +12,12 @@
 There are three layers of sets of filtering rules, all of which are
 normal egrep pattern-matches, applied in turn.
 
-1. the "ATTACK ALERTS" layer, designed to detect the traces of active
+1. the "SECURITY ALERTS" layer, designed to detect the traces of active
 	intrusion attempts.
 
    Patterns raising the alarm go in "/etc/logcheck/cracking.d"; any
 	event that matches one of these patterns turns the report
-	into an urgent "Attack Alerts" report, with the relevant
+	into an urgent "Security Alerts" report, with the relevant
 	event moved to a special section.  The cracking.d standard
 	keywords file is seeded with known symptoms of hostile
 	activity (see logcheck's README.keywords file).
@@ -108,7 +108,7 @@
 Standard "generic" rules go in each directory's "./logcheck" file;
 thus for instance any log message at all matching "ATTACK"
 (listed in "/etc/logcheck/cracking.d/logcheck") _always_ triggers
-an "Attack Alert", unless you deliberately tamper with
+a "Security Alert", unless you deliberately tamper with
 "cracking.ignore.d" rules.
 
 Remember that package-specific "ignore" filters will _not_ override