From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Zabbix policy
Date: Wed, 11 Apr 2007 14:52:28 -0400 [thread overview]
Message-ID: <1176317548.9840.53.camel@sgc> (raw)
In-Reply-To: <46042A0D.5050309@redhat.com>
On Fri, 2007-03-23 at 15:27 -0400, Daniel J Walsh wrote:
> New pocicy for zabbix.
Merged. Added a postgreqsql stream connect, as their webpage says it
can store its data in postgres, in addition to mysql.
>
>
>
>
>
>
> differences
> between files
> attachment
> (zabbix.patch),
> "zabbix.patch"
>
> --- nsaserefpolicy/policy/modules/services/zabbix.fc 1969-12-31 19:00:00.000000000 -0500
> +++ serefpolicy-2.5.10/policy/modules/services/zabbix.fc 2007-03-22 15:06:59.000000000 -0400
> @@ -0,0 +1,4 @@
> +
> +/usr/bin/zabbix_server -- gen_context(system_u:object_r:zabbix_exec_t,s0)
> +/var/run/zabbix(/.*)? gen_context(system_u:object_r:zabbix_var_run_t,s0)
> +/var/log/zabbix(/.*)? gen_context(system_u:object_r:zabbix_log_t,s0)
> --- nsaserefpolicy/policy/modules/services/zabbix.if 1969-12-31 19:00:00.000000000 -0500
> +++ serefpolicy-2.5.10/policy/modules/services/zabbix.if 2007-03-22 15:06:59.000000000 -0400
> @@ -0,0 +1,87 @@
> +
> +## <summary>policy for zabbix</summary>
> +
> +########################################
> +## <summary>
> +## Execute a domain transition to run zabbix.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed to transition.
> +## </summary>
> +## </param>
> +#
> +interface(`zabbix_domtrans',`
> + gen_require(`
> + type zabbix_t, zabbix_exec_t;
> + ')
> +
> + domain_auto_trans($1,zabbix_exec_t,zabbix_t)
> +
> + allow zabbix_t $1:fd use;
> + allow zabbix_t $1:fifo_file rw_file_perms;
> + allow zabbix_t $1:process sigchld;
> +')
> +
> +########################################
> +## <summary>
> +## Read zabbix PID files.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +#
> +interface(`zabbix_read_pid_files',`
> + gen_require(`
> + type zabbix_var_run_t;
> + ')
> +
> + files_search_pids($1)
> + allow $1 zabbix_var_run_t:file r_file_perms;
> +')
> +
> +
> +########################################
> +## <summary>
> +## Allow the specified domain to read zabbix's log files.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +## <rolecap/>
> +#
> +interface(`zabbix_read_log',`
> + gen_require(`
> + type zabbix_log_t;
> + ')
> +
> + logging_search_logs($1)
> + allow $1 zabbix_log_t:dir r_dir_perms;
> + allow $1 zabbix_log_t:file { read getattr lock };
> +')
> +
> +########################################
> +## <summary>
> +## Allow the specified domain to append
> +## zabbix log files.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed to transition.
> +## </summary>
> +## </param>
> +#
> +interface(`zabbix_append_log',`
> + gen_require(`
> + type var_log_t, zabbix_log_t;
> + ')
> +
> + logging_search_logs($1)
> + allow $1 zabbix_log_t:dir r_dir_perms;
> + allow $1 zabbix_log_t:file { getattr append };
> +')
> +
> --- nsaserefpolicy/policy/modules/services/zabbix.te 1969-12-31 19:00:00.000000000 -0500
> +++ serefpolicy-2.5.10/policy/modules/services/zabbix.te 2007-03-22 15:06:59.000000000 -0400
> @@ -0,0 +1,64 @@
> +policy_module(zabbix,1.0.0)
> +
> +########################################
> +#
> +# Declarations
> +#
> +
> +type zabbix_t;
> +type zabbix_exec_t;
> +domain_type(zabbix_t)
> +init_daemon_domain(zabbix_t, zabbix_exec_t)
> +
> +# pid files
> +type zabbix_var_run_t;
> +files_pid_file(zabbix_var_run_t)
> +
> +# log files
> +type zabbix_log_t;
> +logging_log_file(zabbix_log_t)
> +
> +########################################
> +#
> +# zabbix local policy
> +#
> +# Check in /usr/share/selinux/devel/include for macros to use instead of allow rules.
> +
> +# Init script handling
> +
> +
> +domain_use_interactive_fds(zabbix_t)
> +
> +allow zabbix_t self:capability { setuid setgid };
> +
> +## internal communication is often done using fifo and unix sockets.
> +allow zabbix_t self:fifo_file rw_file_perms;
> +allow zabbix_t self:unix_stream_socket create_stream_socket_perms;
> +
> +# Some common macros (you might be able to remove some)
> +files_read_etc_files(zabbix_t)
> +
> +libs_use_ld_so(zabbix_t)
> +libs_use_shared_libs(zabbix_t)
> +
> +miscfiles_read_localization(zabbix_t)
> +
> +ifdef(`targeted_policy',`
> + term_dontaudit_use_unallocated_ttys(zabbix_t)
> + term_dontaudit_use_generic_ptys(zabbix_t)
> +')
> +
> +
> +# pid file
> +allow zabbix_t zabbix_var_run_t:file manage_file_perms;
> +allow zabbix_t zabbix_var_run_t:dir rw_dir_perms;
> +files_pid_filetrans(zabbix_t,zabbix_var_run_t, file)
> +
> +# log files
> +allow zabbix_t zabbix_log_t:file manage_file_perms;
> +allow zabbix_t zabbix_log_t:dir { rw_dir_perms setattr };
> +logging_log_filetrans(zabbix_t,zabbix_log_t,{ file dir })
> +
> +optional_policy(`
> + mysql_stream_connect(zabbix_t)
> +')
>
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2007-04-11 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 19:27 Zabbix policy Daniel J Walsh
2007-04-11 18:52 ` 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=1176317548.9840.53.camel@sgc \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.