From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2] apache.te: Add labelling support for /var/log/mlogc
Date: Fri, 13 Jun 2014 08:45:40 -0400 [thread overview]
Message-ID: <539AF274.1000806@tresys.com> (raw)
In-Reply-To: <CAKoOVcfxHWJYXSov1n0oQdBWLACLP+=X6mNL3xBHk6n_1AxTyA@mail.gmail.com>
On 06/11/2014 10:55 AM, Elia Pinto wrote:
>
> Il 11/giu/2014 16:12 "Christopher J. PeBenito" <cpebenito at tresys.com <mailto:cpebenito@tresys.com>> ha scritto:
>>
>> On 06/10/2014 11:22 AM, Elia Pinto wrote:
>> > Add the right labelling support for the
>> > ModSecurity Audit Log Collector(mlogc).
>> > mlogc is started by apache and run with the
>> > same selinux security context.
>> >
>> > Signed-off-by: Elia Pinto <andronicus.spiros at gmail.com <mailto:andronicus.spiros@gmail.com>>
>> > ---
>> > This is the second revision. httpd_log_t context was not
>> > sufficient for mlogc
>>
>> Why was httpd_log_t insufficient for mlogc?
> In particular Because mlogc create new directory in /var/log/mlogc also.
Which domain is this running in? Is it httpd_t? That domain has permissions to create dirs inside httpd_log_t.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-06-13 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 15:22 [refpolicy] [PATCH v2] apache.te: Add labelling support for /var/log/mlogc Elia Pinto
2014-06-11 14:13 ` Christopher J. PeBenito
2014-06-11 14:55 ` Elia Pinto
2014-06-13 12:45 ` Christopher J. PeBenito [this message]
2014-06-16 17:12 ` Elia Pinto
2014-06-17 12:24 ` Christopher J. PeBenito
-- strict thread matches above, loose matches on Subject: below --
2014-06-09 12:00 Elia Pinto
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=539AF274.1000806@tresys.com \
--to=cpebenito@tresys.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.