aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 11:57:03 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-17 12:38:03 -0400
commit8531fee5e382696ea40b842919ce2d2e6dc6d53c (patch)
tree08c902dec6a8bea35a42224007f6773a2f2db7f9
parenta78f659c563f967247c03b25566a29404706847b (diff)
system/audit: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
-rw-r--r--system/audit/README25
1 files changed, 13 insertions, 12 deletions
diff --git a/system/audit/README b/system/audit/README
index 59dba1679735..72284d18d092 100644
--- a/system/audit/README
+++ b/system/audit/README
@@ -1,16 +1,17 @@
Audit for Slackware
-The Linux Auditing System is a kernel subsystem the allows the kernel to
-record events of interest to intrusion detection systems, such as file
-access attempts, specific system calls, or custom events generated by
-trusted system binaries like login or sshd. The audit package provides the
-tools to configure the audit system, and to collect and process its output.
+The Linux Auditing System is a kernel subsystem the allows the
+kernel to record events of interest to intrusion detection systems,
+such as file access attempts, specific system calls, or custom events
+generated by trusted system binaries like login or sshd. The audit
+package provides the tools to configure the audit system, and to
+collect and process its output.
-To collect audit events, your kernel must have the audit system enabled,
-which is present in the stock Slackware kernels.
+To collect audit events, your kernel must have the audit system
+enabled, which is present in the stock Slackware kernels.
-The audit package has no other dependencies. However, certain audit events
-of interest, such as failed login attempts from /bin/login, password changes,
-etcetera are generated by their respective binaries using libaudit. If your
-site policy requires auditing those events, some reconfiguration and/or
-patching may be required.
+The audit package has no other dependencies. However, certain audit
+events of interest, such as failed login attempts from /bin/login,
+password changes, etcetera are generated by their respective binaries
+using libaudit. If your site policy requires auditing those events,
+some reconfiguration and/or patching may be required.