From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Policy module for shibboleth authentication daemon
Date: Fri, 14 Mar 2014 10:36:33 -0400 [thread overview]
Message-ID: <532313F1.7070301@tresys.com> (raw)
In-Reply-To: <5314B0AA.8080408@automata.rwth-aachen.de>
On 03/03/2014 11:41 AM, Martin Lang wrote:
> I designed a policy module for the shibboleth authentication daemon (see
> http://shibboleth.internet2.edu/). Shibboleth is a single sign-on
> service mainly used in academic environment. The service consists of an
> apache module and a background daemon. The background daemon
> communicates with the remote authentication server whereas the apache
> only communicates locally with the authentication daemon via unix stream
> socket.
>
> I attached the policy files to this mail and would like the module to be
> included in the reference policy. I tested the rules on a Debian wheezy
> machine.
>
> I'm open for improvements and other comments.
It looks like a good start. The big thing that prevents its inclusion is the httpd_t usage in the module:
> # Allow the apache shibboleth module to connect to shibd
> gen_require(`
> type httpd_t;
> ')
> stream_connect_pattern(httpd_t, shibboleth_var_run_t, shibboleth_var_run_t, shibboleth_t)
>
> # Allow apache module to read shibboleth configuration
> shibboleth_read_config(httpd_t)
This access would need to go into the apache module.
The organization would need to be adjusted too[1], but that is minor.
[1] http://oss.tresys.com/projects/refpolicy/wiki/StyleGuide
Finally, I'd prefer that you submit it via "git format-patch -n -s" and send via "git send-email". It's not required, but it makes it easier to commit.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2014-03-14 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 16:41 [refpolicy] Policy module for shibboleth authentication daemon Martin Lang
2014-03-14 14:36 ` Christopher J. PeBenito [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=532313F1.7070301@tresys.com \
--to=cpebenito@tresys.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.