All of lore.kernel.org
 help / color / mirror / Atom feed
From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Syntax fixes in contrib
Date: Wed, 03 Dec 2014 15:33:30 +0100	[thread overview]
Message-ID: <1417617210.29096.4.camel@joe.localdomain> (raw)
In-Reply-To: <547ED76D.5010709@redhat.com>

On Wed, 2014-12-03 at 10:27 +0100, Miroslav Grepl wrote:

> > > > 
> > The problem with the admin interfaces (any interfaces for that matter) is that unless they are called they aren't tested.
> > 
> > This is also one of the reasons why i prefer only adding interfaces that are actually used.
> > 
> > On that other hand, adding interfaces even if they aren't used does make sense for audit2allow/sepolgen-ifgen, and for the confined admin support
> > 
> > 


> We have tests for testing these _admin() interfaces in RHEL. I believe
> we could add them to Fedora to have them available.

Could be interesting. I fear however that the tests aren't going to be
the problem, but rather running them consistently when a unused
interface is added.

I might be wrong with that assumption though

  parent reply	other threads:[~2014-12-03 14:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  6:38 [refpolicy] Syntax fixes in contrib Jason Zaman
2014-11-26  6:38 ` [refpolicy] [PATCH 01/18] ccs: syntax errors in ccs_admin interface Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 02/18] condor: syntax error in condor_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 03/18] distcc: syntax error in distcc_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 04/18] ftp: syntax error in ftp_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 05/18] kerberos: syntax error in kerberos_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 06/18] kismet: syntax error in kismet_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 07/18] nut: syntax error in nut_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 08/18] prelude: syntax error in prelude_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 09/18] psad: syntax error in psad_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 10/18] quota: syntax error in quota_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 11/18] rpcbind: syntax error in rpcbind_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 12/18] rpm: syntax error in rpm_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 13/18] systemtap: syntax error in stapserver_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 14/18] svnserve: syntax error in svnserve_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 15/18] uptime: syntax error in uptime_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 16/18] zabbix: syntax error in zabbix_admin Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 17/18] remove pyzor_role() from pyzor_admin() Jason Zaman
2014-11-26  6:39 ` [refpolicy] [PATCH 18/18] remove spamassassin_role() from spamassassin_admin() Jason Zaman
2014-12-02 15:31 ` [refpolicy] Syntax fixes in contrib Christopher J. PeBenito
2014-12-02 16:15   ` Dominick Grift
2014-12-02 18:17     ` Jason Zaman
2014-12-03  9:27     ` Miroslav Grepl
2014-12-03 12:33       ` Jason Zaman
2014-12-03 14:33       ` Dominick Grift [this message]
2014-12-03 14:44         ` Christopher J. 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=1417617210.29096.4.camel@joe.localdomain \
    --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.