From: Paul Moore <paul.moore@hp.com>
To: Linda Knippers <linda.knippers@hp.com>
Cc: linux-audit@redhat.com
Subject: Re: [RFC 1/1] NetLabel: add audit support for configuration changes
Date: Thu, 28 Sep 2006 10:27:08 -0400 [thread overview]
Message-ID: <451BDBBC.2040301@hp.com> (raw)
In-Reply-To: <451B028B.7040404@hp.com>
Linda Knippers wrote:
> Thanks for sending the audit records.
>
>> # netlabelctl unlbl accept on
>>
>>type=UNKNOWN[1406] msg=audit(1159362394.806:420): netlabel: module=unlbl
>>action=accept auid=0 uid=0 euid=0 tty=pts0 pid=6711 comm="netlabelctl"
>>exe="/usr/local/sbin/netlabelctl"
>>
>> (there is also an audit message for "unlbl accept off" which changes
>> "action=accept" to "action=deny")
>
> One nit-picky comment is that once the user-space tools know about the
> message type and insert "MAC_UNLBL_ACCEPT" as the type, the module=
> and action= fields will be somewhat redundant. I think the same is
> true for the other types of audit records. You could omit the switch
> statement in netlbl_audit_start_common() and shorten the audit records
> if we rely on the audit record type to provide that module/action information.
I've received similar comments from others as well, I plan on dropping
those two fields in the next release of the patch. Speaking on which, I
should have the next release out later today, I'm just waiting on some
feedback to see if it meets all of the LSPP certification requirements.
--
paul moore
linux security @ hp
prev parent reply other threads:[~2006-09-28 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060926205722.828559000@hp.com>
2006-09-26 20:57 ` [RFC 1/1] NetLabel: add audit support for configuration changes paul.moore
2006-09-26 21:46 ` Linda Knippers
2006-09-27 13:21 ` Paul Moore
2006-09-27 23:00 ` Linda Knippers
2006-09-28 14:27 ` Paul Moore [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=451BDBBC.2040301@hp.com \
--to=paul.moore@hp.com \
--cc=linda.knippers@hp.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 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.