From: stefan@seekline.net (Stefan Schulze Frielinghaus)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] new policy pyicqt
Date: Sun, 25 Oct 2009 12:59:23 +0100 [thread overview]
Message-ID: <1256471963.2407.7.camel@localhost> (raw)
Hi all,
attached is a new policy for the ICQ transport PyICQt. I lost track of
head development ... guess the following lines are redundant now
libs_use_ld_so(pyicqt_t)
libs_use_shared_libs(pyicqt_t)
libs_read_lib_files(pyicqt_t)
and can be changed to
libs_read_lib_files(pyicqt_t)
I tested the policy on CentOS 5 for a couple of months with ejabberd so
hope everything is fine tested ;-)
cheers
Stefan
-------------- next part --------------
/etc/pyicq-t(/.*)? gen_context(system_u:object_r:pyicqt_conf_t,s0)
/usr/share/pyicq-t/PyICQt\.py -- gen_context(system_u:object_r:pyicqt_exec_t,s0)
/var/log/pyicq-t\.log -- gen_context(system_u:object_r:pyicqt_log_t,s0)
/var/run/pyicq-t(/.*)? gen_context(system_u:object_r:pyicqt_var_run_t,s0)
/var/spool/pyicq-t(/.*)? gen_context(system_u:object_r:pyicqt_spool_t,s0)
-------------- next part --------------
## <summary>PyICQt is an ICQ transport for XMPP server.</summary>
-------------- next part --------------
policy_module(pyicqt, 1.0.0)
########################################
#
# Declarations
#
type pyicqt_t;
type pyicqt_exec_t;
init_daemon_domain(pyicqt_t,pyicqt_exec_t)
type pyicqt_conf_t;
files_config_file(pyicqt_conf_t)
type pyicqt_spool_t;
files_type(pyicqt_spool_t)
type pyicqt_var_run_t;
files_pid_file(pyicqt_var_run_t)
type pyicqt_log_t;
logging_log_file(pyicqt_log_t)
########################################
#
# PyICQt policy
#
allow pyicqt_t self:fifo_file { read write };
allow pyicqt_t self:tcp_socket create_socket_perms;
allow pyicqt_t self:udp_socket create_socket_perms;
read_files_pattern(pyicqt_t, pyicqt_conf_t, pyicqt_conf_t)
manage_dirs_pattern(pyicqt_t, pyicqt_spool_t, pyicqt_spool_t)
manage_files_pattern(pyicqt_t, pyicqt_spool_t, pyicqt_spool_t)
manage_files_pattern(pyicqt_t, pyicqt_var_run_t, pyicqt_var_run_t)
libs_use_ld_so(pyicqt_t)
libs_use_shared_libs(pyicqt_t)
libs_read_lib_files(pyicqt_t)
files_read_usr_files(pyicqt_t)
files_search_spool(pyicqt_t)
# /etc/nsswitch.conf
files_read_etc_files(pyicqt_t)
# /etc/resolv.conf
sysnet_read_config(pyicqt_t)
dev_read_urand(pyicqt_t)
corecmd_exec_bin(pyicqt_t)
kernel_read_system_state(pyicqt_t)
miscfiles_read_localization(pyicqt_t)
corenet_tcp_connect_generic_port(pyicqt_t)
corenet_sendrecv_unlabeled_packets(pyicqt_t)
next reply other threads:[~2009-10-25 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 11:59 Stefan Schulze Frielinghaus [this message]
2009-10-25 14:48 ` [refpolicy] new policy pyicqt Dominick Grift
2009-10-25 15:09 ` Stefan Schulze Frielinghaus
2009-10-25 16:30 ` Dominick Grift
2009-10-25 21:14 ` Stefan Schulze Frielinghaus
2009-10-26 19:40 ` Stefan Schulze Frielinghaus
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=1256471963.2407.7.camel@localhost \
--to=stefan@seekline.net \
--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.