From: Alexis Wagner <venon@fugusec.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: network object
Date: Tue, 10 Aug 2004 22:38:57 -0400 [thread overview]
Message-ID: <411986C1.3030601@fugusec.net> (raw)
Hi,
I have some questions about selinux in a labeled network.
First of all, I have read on the web that network labelling is not
supported in kernel 2.6 an higher. I have also read that it will be
possible to reimplement the necessary features using the packet filter.
Is that true ?
Imagine I want to allow the domain one_t to set up and use a tcp
connection with the domain two_t on node two_t.
Is it the correct way to set up the policy ?
node one will have the following configuration :
net_contexts :
nodecon 10.10.10.2 255.255.255.255 system_u:object_r:node_two_t
one.te :
allow one_t self:tcp_socket { create_stream_socket_perms } ;
allow one_t netif_type:netif {tcp_recv tcp_send} ;
allow one_t node_two_t:node {node_bind tcp_send tcp_recv};
allow one_t port_t:tcp_socket {name_bind recv_msg send_msg} ;
allow one_t net_conf_t:file r_file_perms;
allow one_t kernel_t:tcp_socket {recvfrom } ;
#Wich domain I put here ?
allow one_t ???:tcp_socket {acceptfrom recvfrom } ;
node two will have the following configuration :
net_contexts :
nodecon 10.10.10.1 255.255.255.255 system_u:object_r:node_one_t
two.te :
allow two_t self:tcp_socket { create_stream_socket_perms } ;
allow two_t netif_type:netif {tcp_recv tcp_send} ;
allow two_t node_one_t:node {node_bind tcp_send tcp_recv};
allow two_t port_t:tcp_socket {name_bind recv_msg send_msg} ;
allow two_t net_conf_t:file r_file_perms;
allow two_t kernel_t:tcp_socket {recvfrom } ;
#Wich domain I put here ?
allow two_t ???:tcp_socket {acceptfrom recvfrom } ;
It is correct ?
Where could I find more uptodate information about using SELinux in a
labeled network ?
Thank you,
Alexis Wagner
--
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.
next reply other threads:[~2004-08-11 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 2:38 Alexis Wagner [this message]
2004-08-12 13:50 ` network object 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=411986C1.3030601@fugusec.net \
--to=venon@fugusec.net \
--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.