From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] A few tweaks for the gitolite policy
Date: Tue, 21 Feb 2012 14:23:46 -0500 [thread overview]
Message-ID: <4F43EF42.4000602@tresys.com> (raw)
In-Reply-To: <1329321693.8039.35.camel@i5.mricon.com>
On 2/15/2012 11:01 AM, Konstantin Ryabitsev wrote:
> ADCs are "Admin-defined commands" that come bundled with gitolite.
> Though they are normally not packaged, they are part of the gitolite
> distribution and are almost always installed by admins:
>
> http://sitaramc.github.com/gitolite/shipped_ADCs.html
>
> It would be welcome if the default gitosis policy allowed them to work.
> It already partially supports ADCs by permitting:
> exec_files_pattern(gitosis_t, gitosis_var_lib_t, gitosis_var_lib_t)
This is something we want to avoid if possible. Executing files that can also be written by the same domain is a good opening for arbitrary code execution. It sounds like the files should be labeled something else, eg. gitosis_exec_t or gitosis_adc_t.
> From my recent experience, it also requires the following:
>
> * managing files in /tmp, as a couple of these ADCs use here-docs
> (bash writes those out into /tmp/sh-thd-{timestamp} and then
> reads them back in)
> * ability to execute /usr/bin/gl-* (gitosis_exec_t) -- notably the
> "fork" ADC relies on that.
I'd have to see the changes, but that seems reasonable..
> I don't submit a patch, because I wanted to leave it up to the
> maintainer's discretion whether to add support for the default ADCs.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2012-02-21 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:01 [refpolicy] A few tweaks for the gitolite policy Konstantin Ryabitsev
2012-02-21 19:23 ` 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=4F43EF42.4000602@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.