From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/3] rsync: remove rsync_run from admin interface
Date: Tue, 25 Aug 2015 12:17:38 +0200 [thread overview]
Message-ID: <20150825101737.GA2269@x250> (raw)
In-Reply-To: <1440429009-2576-1-git-send-email-jason@perfinion.com>
On Mon, Aug 24, 2015 at 11:10:07PM +0800, Jason Zaman wrote:
> Admining rsync does not require running it in the rsync_t domain and
> this causes problems for backups and the like which would originally run
> in the user's domain now run in rsync_t.
Thanks, merged
> ---
> rsync.if | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/rsync.if b/rsync.if
> index e916de8..c7b19aa 100644
> --- a/rsync.if
> +++ b/rsync.if
> @@ -276,6 +276,4 @@ interface(`rsync_admin',`
>
> files_search_pids($1)
> admin_pattern($1, rsync_var_run_t)
> -
> - rsync_run($1, $2)
> ')
> --
> 2.4.6
>
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
--
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
http://keys.gnupg.net/pks/lookup?op=vindex&search=0x314883A202DFF788
Dominick Grift
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20150825/0dcddf4e/attachment.bin
prev parent reply other threads:[~2015-08-25 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 15:10 [refpolicy] [PATCH 1/3] rsync: remove rsync_run from admin interface Jason Zaman
2015-08-24 15:10 ` [refpolicy] [PATCH 2/3] git: allow git_system_t to listen on tcp_sockets Jason Zaman
2015-08-25 10:22 ` Dominick Grift
2015-08-24 15:10 ` [refpolicy] [PATCH 3/3] hadoop: init_startstop_service() can not take attributes Jason Zaman
2015-08-25 10:27 ` Dominick Grift
2015-08-25 10:17 ` Dominick Grift [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=20150825101737.GA2269@x250 \
--to=dac.override@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.