From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Boyce, Kevin P. (Melbourne, FL)" <Kevin.Boyce@ngc.com>
Subject: Re: Current capabilities
Date: Thu, 14 Dec 2006 08:33:15 -0500 [thread overview]
Message-ID: <200612140833.15229.sgrubb@redhat.com> (raw)
In-Reply-To: <04485C8018722949A3DF79E193BB44DB07A50720@xcgfl107.northgrum.com>
On Thursday 14 December 2006 07:43, Boyce, Kevin P. (Melbourne, FL) wrote:
> If you need a record of failed login attempts, try using the syslog
> daemon.
Syslog is generally not good enough for people that *really* need to track
this information. Syslog can be lossy due to udp. And the average user can do
this to you:
while [ 1 ]; do
logger "blah blah blah"
done
When your disk fills up...where's the login information going to go? The audit
system has higher integrity due to needing CAP_AUDIT_WRITE to send login
information. The kernel collects some of the data from the process
credentials so its more trustworthy. It can alert the admin when the audit
partition is starting to get full and then take the machine down if it does
fill.
-Steve
next prev parent reply other threads:[~2006-12-14 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 23:16 Current capabilities Michael W Folsom
2006-12-13 23:39 ` Linda Knippers
2006-12-14 12:43 ` Boyce, Kevin P. (Melbourne, FL)
2006-12-14 13:33 ` Steve Grubb [this message]
2006-12-13 23:41 ` Steve Grubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612140833.15229.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=Kevin.Boyce@ngc.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox