From: Shaun Savage <savages@pcez.com>
To: SELinux@tycho.nsa.gov
Subject: iptables.te errors
Date: Sun, 16 Dec 2001 10:06:53 -0800 [thread overview]
Message-ID: <3C1CE2BD.20707@pcez.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
HI
I am having a hard time with getting courier to work that I decided to
try somwthing easier. iptables. Attached is the te file that I am using.
During make load I get the error
security: context system_u:system_r:iptables_t is invalid
the during the command iptables -t nat -L
I get the errors
avc: denied { create } for pid=9757 exe=/sbin/iptables
scontext=root:sysadmin_r:sysadmin_t tcontext=root_u:sysadm_r:sysadm_t
tclass=rawip_socket
avc: denied { getopt } for pid=9757 exe=/sbin/iptables
scontext=root:sysadmin_r:sysadmin_t tcontext=root_u:sysadm_r:sysadm_t
tclass=rawip_socket
much more later
Shaun savage
[-- Attachment #2: iptables.te --]
[-- Type: text/plain, Size: 756 bytes --]
#
# Authors: Justin Smith <jsmith@mcs.drexel.edu>
#
#
# Rules for the iptables_t domain.
#
type iptables_t, domain, privlog;
type iptables_exec_t, file_type, sysadmfile, exec_type;
type iptables_var_run_t, file_type, sysadmfile, pidfile;
domain_auto_trans(iptables_t, insmod_exec_t, insmod_t)
domain_auto_trans(iptables_t, ifconfig_exec_t, ifconfig_t)
file_type_auto_trans(iptables_t, var_run_t, iptables_var_run_t)
# Inherit and use descriptors from init.
allow iptables_t init_t:fd inherit_fd_perms;
allow iptables_t bin_t:file { execute execute_no_trans };
allow iptables_t iptables_exec_t:file { execute_no_trans };
allow iptables_t iptables_t:capability { net_admin net_raw };
allow iptables_t iptables_t:rawip_socket { create setopt getopt };
next reply other threads:[~2001-12-16 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 18:06 Shaun Savage [this message]
2001-12-17 2:18 ` iptables.te errors Paul Krumviede
2001-12-17 5:48 ` Shaun Savage
2001-12-17 12:55 ` Stephen Smalley
2001-12-17 16:41 ` Shaun Savage
2001-12-17 12:42 ` Stephen Smalley
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=3C1CE2BD.20707@pcez.com \
--to=savages@pcez.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.