From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [ userdom_user_tmp_content patch 1/1] Create userdom_user_tmp_content, and replace existing user tmp content type declarations by it.
Date: Mon, 12 Jul 2010 21:26:38 +0200 [thread overview]
Message-ID: <4C3B6C6E.80601@gmail.com> (raw)
In-Reply-To: <4C3B5A49.6030004@tresys.com>
On 07/12/2010 08:09 PM, Christopher J. PeBenito wrote:
<snip>
>>
>> ########################################
>> ##<summary>
>> +## Make the specified type usable user
>> +## temporary content.
>> +##</summary>
>> +##<param name="domain">
>> +## <summary>
>> +## Domain using the user temporary
>> +## content.
>> +## </summary>
>> +##</param>
>> +##<param name="file_type">
>> +## <summary>
>> +## Type to be used for user temporary
>> +## content.
>> +## </summary>
>> +##</param>
>> +#
>> +interface(`userdom_user_tmp_content',`
>> + files_tmp_file($2)
>> + files_poly_member_tmp($1, $2)
>> + ubac_constrained($2)
>> +')
>
> Why do we have files_poly_member_tmp()? I didn't see any places where
> it was removed above.
I guess there aren't any in refpolicy (except userdom_manage_tmp_role).
Does that mean there should not be any?
>> _______________________________________________
>> refpolicy mailing list
>> refpolicy at oss.tresys.com
>> http://oss.tresys.com/mailman/listinfo/refpolicy
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20100712/28e5ab75/attachment.bin
next prev parent reply other threads:[~2010-07-12 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 14:34 [refpolicy] [ userdom_user_tmp_content patch 1/1] Create userdom_user_tmp_content, and replace existing user tmp content type declarations by it Dominick Grift
2010-07-12 18:09 ` Christopher J. PeBenito
2010-07-12 19:26 ` Dominick Grift [this message]
2010-07-19 17:36 ` 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=4C3B6C6E.80601@gmail.com \
--to=domg472@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.