From: pebenito@ieee.org (Chris PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/5] gssproxy: allow kerberos nfs filetrans
Date: Wed, 13 Dec 2017 18:18:59 -0500 [thread overview]
Message-ID: <a9ba02e1-7298-ad1e-57e2-451282cf53ad@ieee.org> (raw)
In-Reply-To: <20171213181722.28545-1-jason@perfinion.com>
On 12/13/2017 01:17 PM, Jason Zaman wrote:
> ---
> gssproxy.te | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/gssproxy.te b/gssproxy.te
> index c1dcc55..dc7f0e6 100644
> --- a/gssproxy.te
> +++ b/gssproxy.te
> @@ -63,4 +63,5 @@ optional_policy(`
> kerberos_manage_host_rcache(gssproxy_t)
> kerberos_read_keytab(gssproxy_t)
> kerberos_use(gssproxy_t)
> + kerberos_tmp_filetrans_host_rcache(gssproxy_t, file, "nfs_0")
> ')
Is there a reason it has to be limited to only nfs_0? I didn't notice
any type transition conflicts.
--
Chris PeBenito
next prev parent reply other threads:[~2017-12-13 23:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 18:17 [refpolicy] [PATCH 1/5] gssproxy: allow kerberos nfs filetrans Jason Zaman
2017-12-13 18:17 ` [refpolicy] [PATCH 2/5] dirmngr: allow filetrans in gpg_runtime_t Jason Zaman
2017-12-13 23:21 ` Chris PeBenito
2017-12-13 18:17 ` [refpolicy] [PATCH 3/5] gpg: Add gpg_agent_use_card boolean for OpenPGP cards Jason Zaman
2017-12-13 23:21 ` Chris PeBenito
2017-12-13 18:17 ` [refpolicy] [PATCH 4/5] cachefilesd: make cachefilesd_cache_t a mountpoint Jason Zaman
2017-12-13 23:21 ` Chris PeBenito
2017-12-13 18:17 ` [refpolicy] [PATCH 5/5] Set user_runtime_content_type for all remaining types in /run/user/%{UID}/ Jason Zaman
2017-12-13 23:22 ` Chris PeBenito
2017-12-13 23:18 ` Chris PeBenito [this message]
2017-12-20 16:53 ` [refpolicy] [PATCH 1/5] gssproxy: allow kerberos nfs filetrans Jason Zaman
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=a9ba02e1-7298-ad1e-57e2-451282cf53ad@ieee.org \
--to=pebenito@ieee.org \
--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.