public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Burn Alting <burn@swtf.dyndns.org>
To: linux-audit@redhat.com
Subject: Auparse feature or bug
Date: Thu, 14 Mar 2013 21:21:30 +1100	[thread overview]
Message-ID: <1363256490.3199.23.camel@swtf.swtf.dyndns.org> (raw)

Hi,

When the auparse library parses certain USER_* type events it appears to
have an issue key values with embedded spaces. For example, the event

        type=USER_CHAUTHTOK msg=audit(1363256032.497:202603): user
        pid=24180 uid=0 auid=500 ses=1 msg='op=change password id=500
        exe="/usr/bin/passwd" hostname=? addr=?  terminal=pts/1
        res=success'

when parsed using the code identified in auparse_feed(1), will result in

        event: 1
        records:1
        fields:12
        type=1108 event time: 1363256032.497:202603
        type=USER_CHAUTHTOK (USER_CHAUTHTOK)
        pid=24180 (24180)
        uid=0 (root)
        auid=500 (burn)
        ses=1 (1)
        op=change (change)
        id=500 (burn)
        exe="/usr/bin/passwd" (/usr/bin/passwd)
        hostname=? (?)
        addr=? (?)
        terminal=pts/1 (pts/1)
        res=success (success)

As you can see, we have lost the 'password' element of the
	"op=change password"
key value pair in the original event.

Is this a feature or bug???

Regards
Burn


Regards
Burn Alting

             reply	other threads:[~2013-03-14 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 10:21 Burn Alting [this message]
2013-03-14 10:54 ` Auparse feature or bug Steve Grubb
2013-03-14 11:10   ` Burn Alting
2013-03-14 12:55     ` 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=1363256490.3199.23.camel@swtf.swtf.dyndns.org \
    --to=burn@swtf.dyndns.org \
    --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