From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] fcron socket support
Date: Mon, 21 Apr 2014 09:00:04 -0400 [thread overview]
Message-ID: <53551654.1080001@tresys.com> (raw)
In-Reply-To: <1397984133-12996-3-git-send-email-sven.vermeulen@siphos.be>
On 04/20/2014 04:55 AM, Sven Vermeulen wrote:
> diff --git a/cron.te b/cron.te
> index bd8a5cc..a2cc311 100644
> --- a/cron.te
> +++ b/cron.te
> @@ -347,6 +347,8 @@ tunable_policy(`allow_polyinstantiation',`
>
> tunable_policy(`fcron_crond',`
> allow crond_t { system_cron_spool_t user_cron_spool_t }:file manage_file_perms;
> + allow crond_t crond_var_run_t:sock_file manage_sock_file_perms;
> + files_pid_filetrans(crond_t, crond_var_run_t, sock_file, "fcron.fifo")
> ')
This has at least two problems. Name filetrans in a conditional aren't allowed, and also I got an error with a role in a allow rule:
policy/modules/roles/sysadm.te":424:ERROR 'unknown type sysadm_r' at token ';' on line 2363883:
#line 424
allow sysadm_r crond_var_run_t:dir { getattr search open };
checkpolicy: error(s) encountered while parsing configuration
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-04-21 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 8:55 [refpolicy] [PATCH 0/2] Minor updates on fcron and snort Sven Vermeulen
2014-04-20 8:55 ` [refpolicy] [PATCH 1/2] Snort policy updates Sven Vermeulen
2014-04-20 8:55 ` [refpolicy] [PATCH 2/2] fcron socket support Sven Vermeulen
2014-04-21 13:00 ` Christopher J. PeBenito [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-21 15:08 [refpolicy] [PATCH v2 0/2] Minor updates on fcron and snort Sven Vermeulen
2014-04-21 15:08 ` [refpolicy] [PATCH 2/2] fcron socket support Sven Vermeulen
2014-04-24 16:58 ` Christopher J. PeBenito
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=53551654.1080001@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.