From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Paul Osmialowski <p.osmialowsk@samsung.com>,
linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: auditing kdbus service names
Date: Wed, 12 Aug 2015 17:38:14 -0400 [thread overview]
Message-ID: <18456537.MDqL7RWdSn@x2> (raw)
In-Reply-To: <3754565.WlII3JJvve@sifl>
On Wednesday, August 12, 2015 08:40:34 AM Paul Moore wrote:
> Hello all,
>
> I'm currently working on a set of LSM hooks for the new kdbus IPC mechanism
> and one of the things that I believe we will need to add is a new audit
> field for the kdbus service name (very similar to the old fashioned dbus
> service name). I was thinking "kdbus_svc" for the field name, any
> objections?
What was used on the old dbus events?
-Steve
next prev parent reply other threads:[~2015-08-12 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 12:40 auditing kdbus service names Paul Moore
2015-08-12 21:38 ` Steve Grubb [this message]
2015-08-13 2:48 ` Paul Moore
2015-08-13 20:40 ` Steve Grubb
2015-10-01 22:32 ` Paul Moore
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=18456537.MDqL7RWdSn@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=p.osmialowsk@samsung.com \
--cc=selinux@tycho.nsa.gov \
/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;
as well as URLs for NNTP newsgroup(s).