From: jason@perfinion.com (Jason Zaman)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Add allow_gssd_write_tmp boolean
Date: Thu, 24 Jul 2014 13:00:02 +0400 [thread overview]
Message-ID: <20140724090002.GA9783@pippin.perfinion.com> (raw)
In-Reply-To: <53D0C553.30500@redhat.com>
On Thu, Jul 24, 2014 at 10:35:31AM +0200, Miroslav Grepl wrote:
> On 07/23/2014 10:31 PM, Jason Zaman wrote:
> > gssd needs to be able to add entries to the kerberos credential
> > cache. This adds a boolean to allow that.
> > ---
> > rpc.te | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/rpc.te b/rpc.te
> > index 1a6dcc0..f2e44d5 100644
> > --- a/rpc.te
> > +++ b/rpc.te
> > @@ -15,6 +15,14 @@ gen_tunable(allow_gssd_read_tmp, false)
> >
> > ## <desc>
> > ## <p>
> > +## Determine whether gssd can write
> > +## generic user temporary content.
> > +## </p>
> > +## </desc>
> > +gen_tunable(allow_gssd_write_tmp, false)
> > +
> > +## <desc>
> > +## <p>
> > ## Determine whether nfs can modify
> > ## public files used for public file
> > ## transfer services. Directories/Files must
> > @@ -309,6 +317,11 @@ tunable_policy(`allow_gssd_read_tmp',`
> > userdom_read_user_tmp_symlinks(gssd_t)
> > ')
> >
> > +tunable_policy(`allow_gssd_write_tmp',`
> > + userdom_list_user_tmp(gssd_t)
> > + userdom_write_user_tmp_files(gssd_t)
> > +')
> > +
> > optional_policy(`
> > automount_signal(gssd_t)
> > ')
> We probably want to think about better boolean name for this one. Maybe
>
> gssd_write_user_tmp_files
That does sound better yes. I was basing it off the already existing
read boolean. The original read one should be renamed too then probably.
In that case, do these sound better?
gssd_write_user_tmp_files
gssd_read_user_tmp_files
I can send a patch that renames the read one and adds the new write bool.
next prev parent reply other threads:[~2014-07-24 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 20:31 [refpolicy] [PATCH] Add allow_gssd_write_tmp boolean Jason Zaman
2014-07-24 8:35 ` Miroslav Grepl
2014-07-24 9:00 ` Jason Zaman [this message]
2014-07-25 12:19 ` Christopher J. PeBenito
2014-07-25 12:37 ` Jason Zaman
2014-07-25 18:38 ` Daniel J Walsh
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=20140724090002.GA9783@pippin.perfinion.com \
--to=jason@perfinion.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.