From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-audit@redhat.com
Subject: Re: New draft standards
Date: Tue, 15 Dec 2015 00:11:13 -0500 [thread overview]
Message-ID: <20151215051113.GC31812@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAHC9VhSW4=yVaRxRj=VvDmm1YOq_QgXxYB9H=fZHTOa8Y8THow@mail.gmail.com>
On 15/12/10, Paul Moore wrote:
> On Thu, Dec 10, 2015 at 5:49 PM, Steve Grubb <sgrubb@redhat.com> wrote:
> > On Wed, 09 Dec 2015 12:43:37 +1100
> > Burn Alting <burn@swtf.dyndns.org> wrote:
> >
> >> Steve,
> >>
> >> Can you mock up some examples of an 'enriched' event showing how it is
> >> different from what we have now.
> >
> > type=LOGIN msg=audit(1449782897.896:2496): pid=1768 uid=0
> > subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 old-auid=4294967295
> > auid=4325 old-ses=4294967295 ses=1 res=1 UID="root" OLD-AUID="unset"
> > AUID="sgrubb"
> >
> > type=SYSCALL msg=audit(1449778741.412:4952): arch=c000003e syscall=40
> > success=no exit=-22 a0=3 a1=0 a2=0 a3=4000 items=0 ppid=7362 pid=7994
> > auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
> > tty=(none) ses=4294967295 comm="systemd-coredum"
> > exe="/usr/lib/systemd/systemd-coredump"
> > subj=system_u:system_r:init_t:s0 key="einval-retcode" ARCH=x86_64
> > SYSCALL=sendfile AUID="unset" UID="root" GID="root" EUID="root"
> > SUID="root" FSUID="root" EGID="root" SGID="root" FSGID="root"
>
> This could be confusing on a system with "unset" as a user.
As we do with "none", "(unset)" might be better?
> paul moore
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2015-12-15 5:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 19:22 New draft standards Steve Grubb
2015-12-08 19:58 ` Paul Moore
2015-12-08 20:25 ` Steve Grubb
2015-12-09 0:28 ` Paul Moore
2015-12-09 1:43 ` Burn Alting
2015-12-10 22:49 ` Steve Grubb
2015-12-10 22:59 ` Paul Moore
2015-12-15 5:11 ` Richard Guy Briggs [this message]
2015-12-10 4:35 ` Steve Grubb
2015-12-10 16:50 ` Paul Moore
2015-12-10 17:40 ` F Rafi
2015-12-14 15:34 ` Steve Grubb
2015-12-14 16:38 ` Joe Wulf
2015-12-14 17:01 ` Kevin.Dienst
2015-12-14 22:12 ` Burn Alting
2015-12-15 13:46 ` Steve Grubb
2015-12-18 5:12 ` Burn Alting
2015-12-23 22:44 ` Burn Alting
2015-12-26 16:38 ` Steve Grubb
2015-12-27 0:30 ` Burn Alting
2015-12-27 15:06 ` Steve Grubb
2015-12-28 7:24 ` Burn Alting
2015-12-29 19:28 ` LC Bruzenak
2015-12-08 20:49 ` Richard Guy Briggs
2015-12-08 21:28 ` 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=20151215051113.GC31812@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul@paul-moore.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.