From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 3/8] Label systemd-journald files and directories
Date: Sat, 23 Aug 2014 16:29:26 +0200 [thread overview]
Message-ID: <20140823142925.GA2492@e145.network2> (raw)
In-Reply-To: <1408802382-10212-4-git-send-email-nicolas.iooss@m4x.org>
On Sat, Aug 23, 2014 at 03:59:37PM +0200, Nicolas Iooss wrote:
> ---
> policy/modules/system/logging.fc | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/policy/modules/system/logging.fc b/policy/modules/system/logging.fc
> index 374fb53ee0fd..fc3c0854f5a7 100644
> --- a/policy/modules/system/logging.fc
> +++ b/policy/modules/system/logging.fc
> @@ -1,4 +1,5 @@
> /dev/log -s gen_context(system_u:object_r:devlog_t,mls_systemhigh)
> +/dev/log -l gen_context(system_u:object_r:devlog_t,mls_systemhigh)
>
The solution I chose for my personal policy is to just keep the links
device_t. In my opinion it keeps things a bit simpler.
I may be overlooking an compelling argument to label the link with
a private type.
--
http://subkeys.pgp.net:11371/pks/lookup?search=0x02DFF788&op=index
Dominick Grift
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20140823/9b6f9549/attachment.bin
next prev parent reply other threads:[~2014-08-23 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 13:59 [refpolicy] [PATCH 0/8] Incomplete systemd-journald policy Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 1/8] Label systemd files in init module Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 2/8] Introduce init_search_run interface Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 3/8] Label systemd-journald files and directories Nicolas Iooss
2014-08-23 14:29 ` Dominick Grift [this message]
2014-08-23 15:41 ` Nicolas Iooss
2014-08-23 16:52 ` Dominick Grift
2014-08-25 12:32 ` Christopher J. PeBenito
2014-08-29 19:43 ` Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 4/8] Support logging with /run/systemd/journal/dev-log Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 5/8] Label /dev/log symlink at boot time with systemd Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 6/8] Allow journald to read the kernel ring buffer and to use /dev/kmsg Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 7/8] Allow journald to access to the state of all processes Nicolas Iooss
2014-08-23 13:59 ` [refpolicy] [PATCH 8/8] Remove redundant Gentoo-specific term_append_unallocated_ttys(syslogd_t) Nicolas Iooss
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=20140823142925.GA2492@e145.network2 \
--to=dac.override@gmail.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.