From: Richard Guy Briggs <rgb@redhat.com>
To: zhu xiuming <xiumingzhu@gmail.com>
Cc: "Linux-audit@redhat.com" <Linux-audit@redhat.com>
Subject: Re: how to use auditd to record all user command history
Date: Tue, 8 Oct 2013 17:33:26 -0400 [thread overview]
Message-ID: <20131008213326.GD26809@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAP6dAmc2iS8NqLVPCoaBEB_+pwj+Eqh+spqYt=LLq18m5w0cYw@mail.gmail.com>
On Tue, Oct 08, 2013 at 02:05:48PM -0700, zhu xiuming wrote:
> Thanks for your reply.
> Currently, our Linux kernel versions are mostly Redhat 2.6.18-xxx.el5. I
> wonder whether it supports this feature.
The log_passwd feature has not been backported to RHEL5 because the
pam_tty_audit feature wasn't backported to RHEL5, so I would have to say
it is not supported in your system.
An upgrade is necessary.
> On Mon, Oct 7, 2013 at 8:13 PM, Richard Guy Briggs <rgb@redhat.com> wrote:
> > On Mon, Oct 07, 2013 at 10:30:24AM -0700, zhu xiuming wrote:
> > > This is correct. The problem is, this records every keystrokes and even
> > > the password of the users. While I only care about the user command
> > > history, I surely do not want to know their passwords.
> >
> > There is now support in the upstream kernel (3.10-rc1) and in pam
> > (1.1.8+) to not record passwords by default. If you want the old
> > behaviour, add the optional argument to pam_tty_audit: "log_passwd"
> >
> > > On Sun, Oct 6, 2013 at 2:40 PM, Trevor Vaughan <tvaughan@onyxpoint.com
> > >wrote:
> > > > Does pam_tty_audit with enable=* not do what you want?
> > > >
> > > > Trevor
> > > >
> > > > On Sun, Oct 6, 2013 at 5:26 PM, zhu xiuming <xiumingzhu@gmail.com>
> > wrote:
> > > >
> > > >> HI
> > > >> I know this seems an old topic. But unfortunately, I can't find a
> > > >> solution for this. I have googled long time. I tried following
> > options:
> > > >>
> > > >> 1. audit execv syscall,
> > > >> this does record every command typed any tty. However, it
> > generates
> > > >> lots of noise. Sometimes, the execv syscall is so frequently called
> > that
> > > >> the system can't afford to log every call of it and it crashes !!!
> > > >>
> > > >> 2. use *pam_tty_audit.so
> > > >> *
> > > >> this makes it possible to record one or two users, not all users. *
> > > >> *
> > > >> So, may I ask, is this problem solvable by auditd or do I need other
> > > >> tools ?*
> > > >>
> > > >> *
> > > >> *Thanks a lot
> > > >
> > > > Trevor Vaughan
> >
> > - RGB
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer
Kernel Security
AMER ENG Base Operating Systems
Remote, Ottawa, Canada
Voice: +1.647.777.2635
Internal: (81) 32635
Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2013-10-08 21:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 21:26 how to use auditd to record all user command history zhu xiuming
2013-10-06 21:40 ` Trevor Vaughan
2013-10-07 17:30 ` zhu xiuming
2013-10-08 3:13 ` Richard Guy Briggs
2013-10-08 21:05 ` zhu xiuming
2013-10-08 21:33 ` Richard Guy Briggs [this message]
2013-10-09 21:51 ` zhu xiuming
2013-10-09 21:57 ` Steve Grubb
2013-10-09 22:11 ` zhu xiuming
2013-10-09 23:23 ` Smith, Gary R
2013-10-09 23:56 ` zhu xiuming
2013-10-29 14:56 ` shawn wilson
-- strict thread matches above, loose matches on Subject: below --
2013-10-20 1:03 Aschu
2013-10-29 8:33 ` Shinoj Gangadharan
2013-10-29 12:54 ` Steve Grubb
2013-10-29 13:05 ` Richard Guy Briggs
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=20131008213326.GD26809@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=Linux-audit@redhat.com \
--cc=xiumingzhu@gmail.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