All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael C Thompson <thompsmc@us.ibm.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: type=USER_ROLE_CHANGE
Date: Mon, 17 Jul 2006 13:02:15 -0500	[thread overview]
Message-ID: <44BBD0A7.7080305@us.ibm.com> (raw)
In-Reply-To: <200607160841.44085.sgrubb@redhat.com>

Steve Grubb wrote:
> On Thursday 13 July 2006 17:03, Michael C Thompson wrote:
>> In doing some tests, I've noticed that the USER_ROLE_CHANGE audit record
>> is associated with both newrole, and semanage user -[ad].
> 
> semanage should also be using these:
> 
> #define AUDIT_ROLE_ASSIGN            2301 /* Admin assigned user to role */
> #define AUDIT_ROLE_REMOVE          2302 /* Admin removed user from role */
> 
> USER_ROLE_CHANGE should only be used when newrole is used. If semanage needs 
> more record types let me know.
> 
> -Steve

Hey Steve,

I do not believe these messages are implemented, or at least are not 
properly used, in semanage. Doing semanage user changes or semanage 
login changes only result in USER_ROLE_CHANGE messages.

'semanage user -d deleteme_u' yeilds:

type=USER_ROLE_CHANGE msg=audit(1153152594.356:685): user pid=10862 
uid=0 auid=0 subj=root:staff_r:staff_t:s0-s15:c0.c255 msg='op=delete 
SELinux user record acct=deleteme_u old-seuser=? old-role=? old-range=? 
new-seuser=? new-role=? new-range=? exe=/usr/sbin/semanage (hostname=?, 
addr=?, terminal=pts/2 res=success)'

This is seen with policycoreutils-1.30.17-2.

Thanks,
Mike

      reply	other threads:[~2006-07-17 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 21:03 type=USER_ROLE_CHANGE Michael C Thompson
2006-07-16 12:41 ` type=USER_ROLE_CHANGE Steve Grubb
2006-07-17 18:02   ` Michael C Thompson [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=44BBD0A7.7080305@us.ibm.com \
    --to=thompsmc@us.ibm.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 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.