All of lore.kernel.org
 help / color / mirror / Atom feed
From: russell@coker.com.au (Russell Coker)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] apache: update
Date: Thu, 14 Sep 2017 13:07:11 +1000	[thread overview]
Message-ID: <2826874.zb9Cjn7mqj@xev> (raw)
In-Reply-To: <d18c80d0-d288-fc5f-d45b-2925b0849636@ieee.org>

On Wednesday, 13 September 2017 6:45:56 PM AEST Chris PeBenito wrote:
> On 09/13/2017 04:09 AM, Christian G?ttsche wrote:
> > Or should I create a boolean for the log manage permissions?
> 
> No.  If we find that under certain situations the manage permissions are 
> needed, we can reconsider then.

I agree.  Having lots of booleans is annoying, confusing, and not good for 
security in practice.

When something like this is up for debate I think it's best to have a default 
policy of removing the access in question and waiting for more evidence of why 
it's needed.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

  reply	other threads:[~2017-09-14  3:07 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
2017-09-13  8:09             ` Christian Göttsche
2017-09-13 22:45               ` Chris PeBenito
2017-09-14  3:07                 ` Russell Coker [this message]
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=2826874.zb9Cjn7mqj@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.