From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Nimrod Ostrovsky <nimrod.ostrovsky@argus-sec.com>
Subject: Re: Missing "nametype" field in audit PATH records
Date: Wed, 06 Jun 2018 14:26:01 -0400 [thread overview]
Message-ID: <52720348.alSSl4yk16@x2> (raw)
In-Reply-To: <CAN20O3YtY6UVvd+M8csqkPCf-=2BU9OoTYnmg+EXmKQkwhtxnQ@mail.gmail.com>
On Tuesday, May 29, 2018 10:42:11 AM EDT Nimrod Ostrovsky wrote:
> Hello,
>
> I use the latest audit-userspace version on kernel 3.0.21, and Im trying
> to compile a dispatcher app for audispd.
> The problem is that PATH records does not have the "nametype" field in in
> this kernel version, and I want to be able to distinct between "parent"
> PATH records and any other types.
>
> Any ideas how to solve this issue?
> (Without having to upgrade the kernel)
Looks like that landed in the 3.10 kernel. Short of backporting nametype
support to your kernel, there is nothing else that you can do.
-Steve
prev parent reply other threads:[~2018-06-06 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 14:42 Missing "nametype" field in audit PATH records Nimrod Ostrovsky
2018-06-06 18:26 ` 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=52720348.alSSl4yk16@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=nimrod.ostrovsky@argus-sec.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