public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Tomas Mraz <tmraz@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: Re: pam_tty_audit icanon log switch
Date: Mon, 29 Apr 2013 09:14:18 +0200	[thread overview]
Message-ID: <1367219658.19498.6.camel@vespa.frost.loc> (raw)
In-Reply-To: <20130426174213.GE6907@madcap2.tricolour.ca>

On Fri, 2013-04-26 at 13:42 -0400, Richard Guy Briggs wrote: 
> On Fri, Mar 22, 2013 at 08:19:31AM +0100, Tomas Mraz wrote:
> > On Fri, 2013-03-22 at 01:46 -0400, Richard Guy Briggs wrote: 
> > > Hi folks,
> > > 
> > > There's been a couple of requests to add a switch to pam_tty_audit to
> > > *not* log passwords when logging user commands.
> > > 
> > > Most commands are entered one line at a time and processed as complete
> > > lines in non-canonical mode.  Commands that interactively require a
> > > password, enter canonical mode to do this.  This feature (icanon) can be
> > > used to avoid logging passwords by audit while still logging the rest of
> > > the command.
> > > 
> > > Adding a member to the struct audit_tty_status passed in by
> > > pam_tty_audit allows control of canonical mode per task.
> > > 
> > 
> > For the upstream inclusion of the pam_tty_audit patch you will need to
> > add a detection of the new member of the struct audit_tty_status in the
> > configure.in and #ifdef the code properly. The new option can be kept
> > even in the case the new member is not available, but it should log a
> > warning into the syslog with pam_syslog() when used. The documentation
> > should reflect the fact that the option might not be available on old
> > kernels as well.
> 
> Tomas,
> 
> Please have a look at this patch and see if this addresses the issues
> you raised:

Yes, this is fine and can be submitted to Linux-PAM upstream for review
once the whole patch is final.
-- 
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
                                              Turkish proverb

  reply	other threads:[~2013-04-29  7:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  5:46 pam_tty_audit icanon log switch Richard Guy Briggs
2013-03-22  7:19 ` Tomas Mraz
2013-04-26 17:42   ` Richard Guy Briggs
2013-04-29  7:14     ` Tomas Mraz [this message]
2013-03-22 16:05 ` Miloslav Trmac
2013-04-11 20:43 ` Eric Paris
2013-04-18 19:14   ` Richard Guy Briggs
2013-04-18 19:31     ` Miloslav Trmač
2013-04-18 20:07       ` Richard Guy Briggs
2013-04-22 17:16         ` Richard Guy Briggs
2013-04-22 17:28           ` Miloslav Trmač
2013-04-22 18:29             ` Richard Guy Briggs
2013-04-26 17:23               ` Richard Guy Briggs
2013-04-26 17:37       ` Richard Guy Briggs
2013-04-29 21:02         ` Miloslav Trmač

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=1367219658.19498.6.camel@vespa.frost.loc \
    --to=tmraz@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=rgb@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