From: Reino Wallin <reino@oribium.com>
To: SELinux <SELinux@tycho.nsa.gov>
Subject: Policy question
Date: 02 May 2002 12:11:14 +0200 [thread overview]
Message-ID: <1020334278.21391.92.camel@matilda> (raw)
I have defined a few nodes as well as a few interfaces in network.te,
and net_contexts.
In the te files for the standalone proxies (http and generic) the
following will do:
# Allow the domain to send to any node.
allow http_proxy_t node_type:node { tcp_send tcp_recv };
However, the same approach doesn't work in the inetd.te. Avc error
messages appears, and the following rules are supposed to be added.
# Allow the domain to send to any node.
allow inetd_t node_admin_t:node { tcp_send tcp_recv };
allow inetd_t node_dmz_t:node { tcp_send tcp_recv };
allow inetd_t node_vpn_t:node { tcp_send tcp_recv };
allow inetd_t node_internal_t:node { tcp_send tcp_recv };
allow inetd_t node_external_t:node { tcp_send tcp_recv };
If I add theese rules, then also the proxies that is executed from the
inetd works fine in enforcing mode.
Why are theese fine grained rules needed in the inetd.te but not in the
other te files?
Reino
--
You have received this message because you are subscribed to the selinux 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.
next reply other threads:[~2002-05-02 10:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 10:11 Reino Wallin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-18 9:22 policy question Tom
2002-04-18 10:44 ` Russell Coker
2002-04-18 12:25 ` Tom
2002-04-18 14:51 ` Russell Coker
2002-04-18 15:15 ` Tom
2002-04-18 15:32 ` Stephen Smalley
2002-04-18 16:21 ` Tom
2002-04-18 18:28 ` Russell Coker
2002-04-18 20:40 ` Tom
2002-04-18 21:47 ` Russell Coker
2002-04-19 6:30 ` Tom
2002-04-18 16:08 ` Russell Coker
2002-04-18 16:32 ` Tom
2002-04-18 18:47 ` Russell Coker
2002-04-18 20:49 ` Tom
2002-04-18 21:44 ` Russell Coker
2002-04-19 6:14 ` Tom
2002-04-19 9:10 ` Russell Coker
2002-04-19 12:27 ` Tom
2002-04-19 15:02 ` Stephen Smalley
2002-04-18 15:22 ` 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=1020334278.21391.92.camel@matilda \
--to=reino@oribium.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.