All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Contribute ctdbd policy from Fedora to Refpolicy
Date: Mon, 09 Jan 2012 16:22:38 -0500	[thread overview]
Message-ID: <4F0B5A9E.10308@redhat.com> (raw)
In-Reply-To: <20120109210834.GG3416@siphos.be>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/09/2012 04:08 PM, Sven Vermeulen wrote:
> On Fri, Jan 06, 2012 at 12:28:38PM -0500, Daniel J Walsh wrote:
>> Please Review and Ack.
> [...]
> 
> There's some indentation wrong (especially in the interfaces),
> looks like there are some lines with tab and some with spaces.
> 
>> +exec_files_pattern(ctdbd_t, ctdbd_var_lib_t, ctdbd_var_lib_t)
> 
> Oh noes, not again ;-)
> 
> Same here like with boinc, is there a possibility to have some
> segregation between the "regular" ctdbd_var_lib_t and the files
> ctdbd_t wants to execute?
> 
> If not (or not feasible), ok by me.
> 
> Wkr, Sven Vermeulen 
> _______________________________________________ refpolicy mailing
> list refpolicy at oss.tresys.com 
> http://oss.tresys.com/mailman/listinfo/refpolicy

Maybe if these have a constant name, but we have to ask Miroslav.
Maybe we could use file_name_trans rules, but I still think we end up
with a type that has to be written and executed by the same domain.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8LWp4ACgkQrlYvE4MpobMnBwCg4/1K8+VHObTlWePkrRupWaeV
tUoAoKnyvJV2W8i7tXNrwq7exIKF3X1A
=cEv+
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-01-09 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 17:28 [refpolicy] Contribute ctdbd policy from Fedora to Refpolicy Daniel J Walsh
2012-01-09 21:08 ` Sven Vermeulen
2012-01-09 21:22   ` Daniel J Walsh [this message]
2012-01-09 21:46     ` Sven Vermeulen

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=4F0B5A9E.10308@redhat.com \
    --to=dwalsh@redhat.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.