All of lore.kernel.org
 help / color / mirror / Atom feed
From: mgrepl@redhat.com (Miroslav Grepl)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Contribute boinc policy from Fedora to Refpolicy
Date: Wed, 11 Jan 2012 12:29:11 +0100	[thread overview]
Message-ID: <4F0D7287.1070207@redhat.com> (raw)
In-Reply-To: <4F0B58BE.4030005@redhat.com>

On 01/09/2012 10:14 PM, Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/09/2012 03:42 PM, Sven Vermeulen wrote:
>> On Fri, Jan 06, 2012 at 12:24:31PM -0500, Daniel J Walsh wrote:
>>> Please Review and ack.
>> [...]
>>
>> What magic does boinc do with its boinc_var_lib_t files?
>>
>>> +exec_files_pattern(boinc_t, boinc_var_lib_t, boinc_var_lib_t)
>> ^^ this
>>
>>> +domtrans_pattern(boinc_t, boinc_project_var_lib_t,
>>> boinc_project_t)
>> ^^ and this
>>
>> I don't know boinc, but unless it only uses boinc_var_lib_t to
>> create executables there (and nothing else) wouldn't we need a
>> separate type for this?
>>
>> Wkr, Sven Vermeulen
>> _______________________________________________ refpolicy mailing
>> list refpolicy at oss.tresys.com
>> http://oss.tresys.com/mailman/listinfo/refpolicy
> Miroslav has done most of the work on these.
Boinc/boinc projects create files on the fly which are executed by these 
projects. I was trying to find a solution but I always ended up with this.

Regards,
Miroslav
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk8LWL4ACgkQrlYvE4MpobOOhQCg2JEBNO+83jCgbcEngoBiSfaK
> +xQAoOhbKI9Es5oUCjGkahzkAaS4cwb2
> =gJ8m
> -----END PGP SIGNATURE-----

      reply	other threads:[~2012-01-11 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 17:24 [refpolicy] Contribute boinc policy from Fedora to Refpolicy Daniel J Walsh
2012-01-09 20:42 ` Sven Vermeulen
2012-01-09 21:14   ` Daniel J Walsh
2012-01-11 11:29     ` Miroslav Grepl [this message]

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=4F0D7287.1070207@redhat.com \
    --to=mgrepl@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.