From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Maupertuis Philippe <philippe.maupertuis@equensworldline.com>
Subject: Re: Strange behavior with pam_tty_audit
Date: Tue, 14 Nov 2017 08:53:02 -0500 [thread overview]
Message-ID: <2393137.nNdHcdsWyM@x2> (raw)
In-Reply-To: <3D2AB1326AB2974190FCE3F69401F7900102F4CE0DDD@FRVDX103.fr01.awl.atosorigin.net>
Hello,
On Tuesday, November 14, 2017 8:29:34 AM EST Maupertuis Philippe wrote:
> The auditd rules for PCI reads :
> ## 10.2.2 Log administrative action. To meet this, you need to enable tty
> ## logging. The pam config below should be placed into su and sudo pam
> stacks. ## session required pam_tty_audit.so disable=* enable=root
>
> I have noticed that nothing happened unless I add in /etc/pam.d/sshd
> session required pam_tty_audit.so enable=*
If I understand, you deleted the 'disable=*' and replaced 'root' with '*'.
That would be unusual. The command line is processed from left to right. So,
what should happen in the original rule is disable auditing of all users, then
enable auditing of only root. PCI wants administrative actions which would
only be the root user.
> At which point I get
>
> Should it be done that way ?
> Did I miss something ?
It works for me as specified in the PCI rules. (Tested using su.) Note that
the kernel caches the keystrokes and you do not get a 1x1 mapping of events to
commands entered. You will likely get multiple commands all strung together.
It only creates the event when either it fills the buffer or the user ends the
privileged session.
-Steve
next prev parent reply other threads:[~2017-11-14 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 13:29 Strange behavior with pam_tty_audit Maupertuis Philippe
2017-11-14 13:53 ` Steve Grubb [this message]
2017-11-14 15:47 ` Maupertuis Philippe
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=2393137.nNdHcdsWyM@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=philippe.maupertuis@equensworldline.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