From: Paul Moore <pmoore@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com, Mark Ellzey <socket@gmail.com>
Subject: Re: [PATCH] audit: add nspid and nsppid in audit_log_task_info
Date: Thu, 04 Dec 2014 11:43:57 -0500 [thread overview]
Message-ID: <3977383.Hm9ahhJmJF@sifl> (raw)
In-Reply-To: <20141204031432.GB12425@madcap2.tricolour.ca>
On Wednesday, December 03, 2014 10:14:32 PM Richard Guy Briggs wrote:
> On 14/12/03, Paul Moore wrote:
> > On Sunday, November 23, 2014 09:58:48 AM Eric Paris wrote:
> > > [forwarding to 2 people looking at audit now, do you mind resending to
> > > linux-audit@redhat.com and inluding them both?]
> >
> > I'm also adding the linux-audit list to the CC line.
> >
> > I know Richard has been working on namespaces/audit, I'd like to hear his
> > comments on this patch.
>
> At first when I saw this, I wondered if it was even necessary, thinking
> that information should either be irrelevant, or available elsewhere.
>
> Given that it could be several nested pid namespaces, it may even be
> incomplete.
Okay, thanks for the input. It doesn't look like this is something we want to
merge at this point.
> The most obvious one is that of vanishing fields in audit log messages
> which concerns Steve Grubb. If we fixed the ordering issue, vanishing
> fields should no longer be a concern.
Yes, this is just one more reason why we need to rework the audit record
format. I've got more ideas on this since we last talked on-list, but I've
had to shelve things a bit to deal with the audit bugs.
However, make no mistake, the audit record format will be changing, this fixed
string format is garbage.
--
paul moore
security and virtualization @ redhat
prev parent reply other threads:[~2014-12-04 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP19V6oG+qhcqiYzP3Dk=ioBr7dLeLbzNxQ42hdoPAafitoRag@mail.gmail.com>
[not found] ` <1416754728.3116.22.camel@localhost>
2014-12-03 23:39 ` [PATCH] audit: add nspid and nsppid in audit_log_task_info Paul Moore
2014-12-04 3:14 ` Richard Guy Briggs
2014-12-04 16:43 ` Paul Moore [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=3977383.Hm9ahhJmJF@sifl \
--to=pmoore@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@redhat.com \
--cc=socket@gmail.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