All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: chanson@TrustedCS.com
Cc: paul.moore@hp.com, refpolicy@oss.tresys.com, selinux@tycho.nsa.gov
Subject: Re: [refpolicy] [PATCH] refpolicy: Add missing network related MLSconstraints
Date: Fri, 13 Feb 2009 18:41:36 -0800	[thread overview]
Message-ID: <49962F60.3090206@schaufler-ca.com> (raw)
In-Reply-To: <170D6ABBBA770349AA49582A86FCED15BA0199@HAVOC.tcs-sec.com>

chanson@TrustedCS.com wrote:
>  
> Traditionally network objects in a MLS system are not usually subject to
> the usual privilege overrides.
Hum. That wasn't true of Trusted Irix where sockets were the network
objects.
Of course, you can only apply privilege on the sending end because the
privilege state isn't transmitted.

On Smack the network object is the process, and privilege is required to
muck with the attributes of your own sockets, but otherwise it's the same,
again the privilege isn't getting transmitted, so you can't determine if
it's there on the other end.

If you want to transmit the privilege state, and SELinux (appears to)
allow that, you really ought to allow for that on the other end.


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

  parent reply	other threads:[~2009-02-14  2:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 21:15 [PATCH] refpolicy: Add missing network related MLS constraints Paul Moore
2009-02-12 21:15 ` [refpolicy] " Paul Moore
2009-02-13 19:36 ` [refpolicy] [PATCH] refpolicy: Add missing network related MLSconstraints chanson
2009-02-13 19:36   ` chanson at TrustedCS.com
2009-02-13 20:44   ` Paul Moore
2009-02-13 20:44     ` Paul Moore
2009-02-13 21:38     ` Glenn Faden
2009-02-13 22:02       ` Paul Moore
2009-02-13 22:02         ` Paul Moore
2009-02-13 22:17         ` chanson
2009-02-13 22:17           ` chanson at TrustedCS.com
2009-02-13 23:17           ` Paul Moore
2009-02-13 23:17             ` Paul Moore
2009-02-13 23:54             ` chanson
2009-02-13 23:54               ` chanson at TrustedCS.com
2009-02-13 22:24         ` Glenn Faden
2009-02-13 23:10           ` Paul Moore
2009-02-14  2:41   ` Casey Schaufler [this message]
2009-02-16 15:18     ` chanson
2009-02-16 15:18       ` chanson at TrustedCS.com
2009-02-21  1:37 ` [refpolicy] [PATCH] refpolicy: Add missing network related MLS constraints Joe Nall
2009-02-21  1:37   ` Joe Nall
2009-02-23 17:37   ` Paul Moore
2009-02-23 17:37     ` 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=49962F60.3090206@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=chanson@TrustedCS.com \
    --cc=paul.moore@hp.com \
    --cc=refpolicy@oss.tresys.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.