From: mgrepl@redhat.com (Miroslav Grepl)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] kdbus support
Date: Mon, 3 Aug 2015 15:34:30 +0200 [thread overview]
Message-ID: <55BF6DE6.2070805@redhat.com> (raw)
In-Reply-To: <55BF6C54.9070806@tycho.nsa.gov>
On 08/03/2015 03:27 PM, Stephen Smalley wrote:
> On 08/03/2015 08:31 AM, Miroslav Grepl wrote:
>> I am working on kdbus support on Fedora 24. Basically we need to add
>> support for
>>
>> /sys/fs/kdbus
>>
>> and I am thinking about correct labeling. Something like
>>
>> +type kdbusfs_t;
>> +fs_type(kdbusfs_t)
>> +files_mountpoint(kdbusfs_t)
>> +dev_associate_sysfs(kdbusfs_t)
>> +genfscon kdbusfs / gen_context(system_u:object_r:kdbusfs_t,s0)
>>
>> What do you think about kdbusfs_t label?
>
> Until kdbus has LSM hooks, it should not be accessible by anything.
> Otherwise, it is a completely uncontrolled IPC mechanism by which
> anything is free to violate policy on the system.
>
>
Yes, just wanted to test it and see lot of CAP_IPC_OWNER.
--
Miroslav Grepl
Senior Software Engineer, SELinux Solutions
Red Hat, Inc.
next prev parent reply other threads:[~2015-08-03 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 12:31 [refpolicy] kdbus support Miroslav Grepl
2015-08-03 13:27 ` Stephen Smalley
2015-08-03 13:34 ` Miroslav Grepl [this message]
2015-08-03 14:33 ` Daniel J Walsh
2015-08-03 15:40 ` Stephen Smalley
2015-08-03 15:52 ` Daniel J Walsh
2015-08-03 15:55 ` Stephen Smalley
2015-08-03 18:21 ` Dominick Grift
2015-08-03 18:30 ` Dominick Grift
2015-08-03 18:41 ` Daniel J Walsh
2015-08-03 18:54 ` Dominick Grift
2015-08-27 15:46 ` Dominick Grift
2015-08-03 19:28 ` Paul Moore
2015-08-05 12:19 ` Miroslav Grepl
2015-08-27 15:06 ` Dominick Grift
2015-08-03 18:19 ` Dominick Grift
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=55BF6DE6.2070805@redhat.com \
--to=mgrepl@redhat.com \
--cc=refpolicy@oss.tresys.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.