Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael C Thompson <thompsmc@us.ibm.com>
To: Linux Audit <linux-audit@redhat.com>,
	Steve Grubb <sgrubb@redhat.com>, Amy Griffis <amy.griffis@hp.com>
Subject: type=USER_ROLE_CHANGE
Date: Thu, 13 Jul 2006 16:03:55 -0500	[thread overview]
Message-ID: <44B6B53B.80802@us.ibm.com> (raw)

Hey Steve / Amy,

In doing some tests, I've noticed that the USER_ROLE_CHANGE audit record 
is associated with both newrole, and semanage user -[ad]. I do not think 
that USER_ROLE_CHANGE is a good name to have associated with SELinux 
user creation/removal, not to mention that the payload of the record 
resulting from newrole looks nothing like the payload from that 
generated by semanage user -[ad].

Can we add a USER_ROLE_MODIFY, or some other label, that would indicate 
and differentiate SELinux user creation/removal from a simple newrole?

Thanks,
Mike

             reply	other threads:[~2006-07-13 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 21:03 Michael C Thompson [this message]
2006-07-16 12:41 ` type=USER_ROLE_CHANGE Steve Grubb
2006-07-17 18:02   ` type=USER_ROLE_CHANGE Michael C Thompson

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=44B6B53B.80802@us.ibm.com \
    --to=thompsmc@us.ibm.com \
    --cc=amy.griffis@hp.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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