All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: casey@schaufler-ca.com
Cc: selinux@tycho.nsa.gov
Subject: Re: Question on networking accesses
Date: Mon, 21 May 2007 11:22:25 -0400	[thread overview]
Message-ID: <200705211122.25948.paul.moore@hp.com> (raw)
In-Reply-To: <93504.42890.qm@web36614.mail.mud.yahoo.com>

On Monday, May 21 2007 9:48:52 am Casey Schaufler wrote:
> I have what I hope is a fairly straitforward question on the SELinux
> networking model. Let's pretend that I have a process A that sends a
> UDP packet P to a second process B. From the viewpoint of access control
> is this:
>
>     - process A writing to process B
>     - process B reading from process A
>     - process A creating packet P, and process B reading packet P
>
> some combination of the above, or something else entirely?

>From 10,000 feet up in the air that sounds roughly about right.  Although if 
you are talking about labeled networking it can be a bit more involved, 
especially if you are using labeled IPsec.

Can you be a bit more specific?

-- 
paul moore
linux security @ hp


--
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.

  reply	other threads:[~2007-05-21 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 13:48 Question on networking accesses Casey Schaufler
2007-05-21 15:22 ` Paul Moore [this message]
2007-05-21 16:07   ` Casey Schaufler
2007-05-21 18:20     ` Paul Moore
2007-05-21 20:18       ` Casey Schaufler
2007-05-21 20:30         ` Paul Moore
2007-05-21 21:06           ` Casey Schaufler
2007-05-22  3:46             ` Paul Moore
2007-05-22  4:59               ` Casey Schaufler
2007-05-22 12:39               ` Steve G
2007-05-22 14:13                 ` Paul Moore
2007-05-22 14:56                 ` Casey Schaufler

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=200705211122.25948.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=casey@schaufler-ca.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.