From: Steve Grubb <sgrubb@redhat.com>
To: "Miloslav Trmač" <mitr@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: pam_tty_audit bi-directional logging
Date: Mon, 10 Jun 2013 11:55:40 -0400 [thread overview]
Message-ID: <1405680.FAKGE90IN8@x2> (raw)
In-Reply-To: <1918333854.17061279.1370879295052.JavaMail.root@redhat.com>
On Monday, June 10, 2013 11:48:15 AM Miloslav Trmač wrote:
> > > > Is there any way to make pam_tty_audit log not only what the user
> > > > types but also what the server sends back?
> > >
> > > No, this is currently not possible.
> >
> > Impossible as in 1) what is already shipped can't do this, or 2) no amount
> > of code being added to the kernel can do this, or 3) for upstream
> > political reasons?
>
> Primarily 1), also
> 4) auditing output is a little more difficult because it's much more common
> to have a _lot_ of output (e.g. (find -name '*.c')), so TTY auditing should
> probably be able to throttle the TTY throughput. (In principle the same
> problem is with input as well - with a PTY I can cause massive amount of
> data to be audited - but it doesn't occur accidentally.)
Probably would need to escape/drop all the control characters, too, so report
display terminal doesn't get hijacked. :-) But yes, I could see someone
DoS'ing the machine easily now that you mention it.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2013-06-10 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 21:40 pam_tty_audit bi-directional logging Tracy Reed
2013-06-07 22:48 ` Miloslav Trmač
2013-06-08 12:59 ` Steve Grubb
2013-06-10 15:48 ` Miloslav Trmač
2013-06-10 15:55 ` Steve Grubb [this message]
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=1405680.FAKGE90IN8@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=mitr@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