All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: linux-audit@redhat.com
Cc: Richard Guy Briggs <rgb@redhat.com>
Subject: [PATCH] loginuid change logging details
Date: Fri, 17 Jan 2014 18:34:56 -0500	[thread overview]
Message-ID: <cover.1389996576.git.rgb@redhat.com> (raw)

I missed posting this before the holidays.  I discovered this while adding
other information to other message types.

It seemed to me that loginuid changes were significantly missing context
references.  This patch adds that.  Is this sufficient, or is there more
information missing too?  If this is sufficient, stop reading this cover letter
and review the patch.  If it is not sufficient, keep reading below...

The question has been raised that perhaps we should be switching this to use
audit_log_task_info() istead which adds a whole lot more information about this
task.

In the existing message
	pid
	uid
are already given, before
	old-auid
	new-auid
	old-ses
	new-ses
.

The function audit_log_task_info() gives:
	ppid
	pid
	auid
	uid
	gid
	euid
	suid
	fsuid
	egid
	sgid
	fsgid
	tty
	ses
        comm
	exe
	res
.

So, 
	pid
	uid
are in the right order, along with
	new-auid (auid)
	new-ses (ses)
but if we give the
	old-auid
	old-ses
values first, then call audit_log_task_info(), the old values will preceed 
	pid
	uid
.

Is this re-ordering acceptable to gain more information and reduce code duplicity?


Richard Guy Briggs (1):
  audit: log task context when setting loginuid

 kernel/auditsc.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

             reply	other threads:[~2014-01-17 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 23:34 Richard Guy Briggs [this message]
2014-01-17 23:34 ` [PATCH] audit: log task context when setting loginuid Richard Guy Briggs
2014-01-20 16:44 ` [PATCH] loginuid change logging details Eric Paris
2014-02-03 17:03   ` Steve Grubb
2014-02-03 17:43     ` Eric Paris
2014-02-03 22:38       ` Steve Grubb
2014-02-03 16:40 ` Steve Grubb

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=cover.1389996576.git.rgb@redhat.com \
    --to=rgb@redhat.com \
    --cc=linux-audit@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.