From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: List of search fields?
Date: Mon, 11 Jun 2012 14:22:39 -0400 [thread overview]
Message-ID: <1554582.iNiaJFb4J8@x2> (raw)
In-Reply-To: <20120611180017.GD15842@kildalton>
On Monday, June 11, 2012 07:00:17 PM Stephen Quinney wrote:
> Is there a definitive list of search fields documented somewhere?
Not really. This is because searching should be focused on the type of thing you
want to find. Are you looking for uids? Or files? Or terminals? etc. The search
capability is not exhaustive or complete. Common Criteria only dictates that
about 5 or 6 required fields should be searchable. But we allow searching on more
than that.
> In particular, I'm trying to find a list of which are (or are not)
> "interpreted" (i.e. the type is AUPARSE_TYPE_ESCAPED).
That is different entirely. The field type information is used to translate the
raw value into something more readable. This is very different than searching.
However, the rule for escaping is as follows.
If a user can control the contents of a field's value, it must be escaped.
-Steve
prev parent reply other threads:[~2012-06-11 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 18:00 List of search fields? Stephen Quinney
2012-06-11 18:22 ` Steve Grubb [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=1554582.iNiaJFb4J8@x2 \
--to=sgrubb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox