From: LC Bruzenak <lenny@magitekltd.com>
To: "Miloslav Trmač" <mitr@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: auparse question
Date: Fri, 06 Jun 2008 14:53:33 -0500 [thread overview]
Message-ID: <1212782013.6726.32.camel@homeserver> (raw)
In-Reply-To: <1212781001.15953.12.camel@amilo>
On Fri, 2008-06-06 at 19:36 +0000, Miloslav Trmač wrote:
...
> One usual way of handling spaces is to use the hex-encoded form for
> field representation, and decode it either using
> auparse_interpret_field() (which hard-codes the ways to decode specific
> field types, and does nothing for unknown types), or in the application.
> The other usual way of handling spaces is to just write them in the
> record and let the applications deal with them however they want (you
> can get the raw record text out of auparse, after all).
Fair enough; thanks for the response.
Yes, I am able to get the raw string out and I can sub-parse it myself.
Up to this point the parser was doing all the work for me! :)
Thx!
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2008-06-06 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 19:20 auparse question LC Bruzenak
2008-06-06 19:36 ` Miloslav Trmač
2008-06-06 19:53 ` LC Bruzenak [this message]
2008-06-06 20:07 ` audit string encoding is broken (Was: auparse question) John Dennis
2008-06-06 20:45 ` LC Bruzenak
2011-08-30 21:09 auparse question LC Bruzenak
2011-08-30 21:12 LC Bruzenak
2011-08-30 23:18 ` Miloslav Trmac
2011-08-31 18:29 ` Steve Grubb
2011-08-31 16:49 ` Steve Grubb
2011-08-31 18:07 LC Bruzenak
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=1212782013.6726.32.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=linux-audit@redhat.com \
--cc=mitr@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.