All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Miloslav Trmač" <mitr@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: Thu, 18 Apr 2013 15:31:36 -0400 (EDT)	[thread overview]
Message-ID: <669386482.3913087.1366313496573.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20130418191430.GA4112@madcap2.tricolour.ca>

Hello,

----- Original Message -----
> Full replacement patch:

I'm still convinced that icanon is not the correct condition, see https://www.redhat.com/archives/linux-audit/2013-March/msg00052.html .


> diff --git a/include/uapi/linux/audit.h b/include/uapi/linux/audit.h
> index 9f096f1..a863669 100644
> --- a/include/uapi/linux/audit.h
> +++ b/include/uapi/linux/audit.h
> @@ -369,7 +369,8 @@ struct audit_status {
>  };
>  
>  struct audit_tty_status {
> -	__u32		enabled; /* 1 = enabled, 0 = disabled */
> +	__u32		enabled;	/* 1 = enabled, 0 = disabled */
> +	__u32		log_icanon;	/* 1 = enabled, 0 = disabled */
>  };

Also, would it make sense for the user-space API to be more general about expressing the intent ("log passwords")?  I don't know, being precise about the exact effect of the option is also beneficial.
    Mirek

  reply	other threads:[~2013-04-18 19:31 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
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č [this message]
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=669386482.3913087.1366313496573.JavaMail.root@redhat.com \
    --to=mitr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.