From: russell@coker.com.au (Russell Coker)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] apache: update
Date: Wed, 13 Sep 2017 10:44:36 +1000 [thread overview]
Message-ID: <2276373.k7QpJJhrmk@xev> (raw)
In-Reply-To: <ba9dcae2-d303-99ed-63dc-97b004ffb884@ieee.org>
On Tuesday, 12 September 2017 5:23:14 PM AEST Chris PeBenito wrote:
> On 09/12/2017 05:56 AM, Christian G?ttsche wrote:
> >> It's not as if this change really restricts things anyway, httpd_t can
> >> still copy the log data to a new file and unless you are tracking Inode
> >> numbers or creation time you won't notice. I don't think
> >> create+read+append access is meaningfully more restricting than
> >> manage_file_perms.
> >
> > My idea is, that the domain can not overwrite the existing logs or
> > tamper with them in any way.
>
> I'm inclined to restore the previous permissions (this patch) unless
> there is a solid case for keeping what we have.
OK give that a go and we'll do more tests about how it works.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2017-09-13 0:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 15:11 [refpolicy] [PATCH 1/2] apache: align filecontexts Christian Göttsche
2017-09-10 15:11 ` [refpolicy] [PATCH 2/2] apache: update Christian Göttsche
2017-09-11 23:13 ` Chris PeBenito
2017-09-12 4:17 ` Russell Coker
2017-09-12 9:56 ` Christian Göttsche
2017-09-12 21:23 ` Chris PeBenito
2017-09-13 0:44 ` Russell Coker [this message]
2017-09-13 8:09 ` Christian Göttsche
2017-09-13 22:45 ` Chris PeBenito
2017-09-14 3:07 ` Russell Coker
2017-09-11 23:08 ` [refpolicy] [PATCH 1/2] apache: align filecontexts Chris PeBenito
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=2276373.k7QpJJhrmk@xev \
--to=russell@coker.com.au \
--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.