From: Burn Alting <burn@swtf.dyndns.org>
To: Sowndarya K <sowndaryak18@gmail.com>
Cc: Linux-audit@redhat.com
Subject: Re: Audit log Fields
Date: Fri, 12 Feb 2016 00:06:54 +1100 [thread overview]
Message-ID: <1455196014.28800.61.camel@swtf.swtf.dyndns.org> (raw)
In-Reply-To: <CAKc3OY1obXePLv5ac7B3g3EAm=XjZkDFPHDXaFU4q11UMj3NYw@mail.gmail.com>
Sowndarya,
Are you are asking how do you propose another public field name to be
added to the list in
https://people.redhat.com/sgrubb/audit/audit-events.txt ?
If so, I'd suggest you provide
a. Proposed field name
b. Description of it's content.
c. Describe how it's going to be used.
The list can then make comment and/or provide advice.
Steve,
Perhaps we could update the above document to advise users what they
should offer in such a proposal.
Perhaps further, we could offer a generic solution on how one could
define a 'non-public' field name. That is, a 'non-public' field is one
which could not, via it's nomenclature, conflict with a current or
future 'public' (aka published) field name. Such non-public fields could
then be used by capability that only needs the audit source and audit
consumer to be aware of the field.
Hopefully I am not reading too much into the original request.
Regards
On Thu, 2016-02-11 at 18:07 +0530, Sowndarya K wrote:
> As of now there are so many proposed fields in the audit event log ,
> if I wanted to one proposed field which is of not use as much ,which
> one can I chose for ?
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2016-02-11 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 12:37 Audit log Fields Sowndarya K
2016-02-11 13:06 ` Burn Alting [this message]
2016-02-12 19:04 ` Steve Grubb
2016-02-12 18:57 ` 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=1455196014.28800.61.camel@swtf.swtf.dyndns.org \
--to=burn@swtf.dyndns.org \
--cc=Linux-audit@redhat.com \
--cc=sowndaryak18@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