From: Dominick Grift <domg472@gmail.com>
To: Chris Kuester <c.kuester@tarent.de>
Cc: selinux@tycho.nsa.gov
Subject: Re: Conditional Access to Network Resources
Date: Tue, 21 Oct 2008 13:04:52 +0200 [thread overview]
Message-ID: <1224587092.9326.3.camel@rawhide.grift.internal> (raw)
In-Reply-To: <20081021092518.GA6606@localdomain>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
On Tue, 2008-10-21 at 11:25 +0200, Chris Kuester wrote:
> I want to allow my domain to access certain ports on the local interface
> and certain ports on a nonlocal interface.
I think that you would have to first declare your interfaces with for example "semanage interface -{a|d|m} [-tr] interface_spec"
(man semanage) and then define policy about how domains may interact with the interfaces that you have declared.
By default no interfaces are declared and domain may interact with any
interface.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-21 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 9:25 Conditional Access to Network Resources Chris Kuester
2008-10-21 11:04 ` Dominick Grift [this message]
2008-10-21 12:03 ` Stephen Smalley
2008-10-21 14:03 ` Paul Moore
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=1224587092.9326.3.camel@rawhide.grift.internal \
--to=domg472@gmail.com \
--cc=c.kuester@tarent.de \
--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.