All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] authbind policy should be removed
Date: Tue, 14 Jan 2014 08:41:32 -0500	[thread overview]
Message-ID: <52D53E8C.1040403@tresys.com> (raw)
In-Reply-To: <1389698125.28251.31.camel@x220.localdomain>

On 01/14/14 06:15, Dominick Grift wrote:
> On Tue, 2014-01-14 at 21:52 +1100, Russell Coker wrote:
>> On Tue, 14 Jan 2014, Dominick Grift <dominick.grift@gmail.com> wrote:
>>> You do not have to install that module. If you don't want it then just
>>> remove it from your modules.conf, or do semodule -r authbind if its
>>> already installed.
>>
>> What is the point in having dead code in the repository?
> 
> You have a point but it's not that compelling to me. There is plenty
> (what i would consider) dead policy in contrib and as long as its not in
> the way i personally do not really think it has much priority to remove
> it.
> 
> With the base repository it is bit of a different story as far as i am
> concerned.

Looking at the policy, my guess is that its nowhere near working.  As Russell has pointed out, is been in existence for eons and hasn't improved.  Since no one seems to have any interest in using it and it's broken, I'm fine removing it.  It's still revision controlled, so if there is future interest, it can still be retrieved from the git history (not that there is much to the policy if it needs to be remade).

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2014-01-14 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  4:12 [refpolicy] authbind policy should be removed Russell Coker
2014-01-14 10:16 ` Dominick Grift
2014-01-14 10:52   ` Russell Coker
2014-01-14 11:15     ` Dominick Grift
2014-01-14 13:41       ` Christopher J. PeBenito [this message]
2016-11-23  0:57         ` Russell Coker
2016-11-23  3:20           ` 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=52D53E8C.1040403@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.