All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov
Subject: Backwards compatibility (proposal for a new compat_net like flag)
Date: Thu, 30 Aug 2007 16:02:25 -0400	[thread overview]
Message-ID: <200708301602.27272.paul.moore@hp.com> (raw)

As you may have noticed there has been a _lot_ of discussion lately about the 
labeled networking functionality in SELinux and how to both improve the 
existing functionality as well as introduce new functionality to enable 
SELinux to be used in more and more places.  Several different things were 
debated including fallback peer labels, packet flow control, loopback 
labeling, and the use of unified access checks for the different peer 
labeling mechanisms (NetLabel, labeled IPsec).

While it should be possible to implement some of the new ideas while retaining 
backwards compatibility (fallback labels, loopback labeling) some other ideas 
would most likely introduce problems when used with older policy (packet flow 
control, unified access checks).  Unfortunately, as discussed numerous times 
before, we don't presently have a good way to select kernel behavior at 
runtime and if we want to move forward with some of the new labeled 
networking ideas we need a way to preserve the existing behavior.

To help solve this problem I'd like to propose we introduce a new tunable, 
similar to the existing compat_net flag, but instead of it being a simple 
boolean value I would like to implement it as an integer value.  This new 
tunable, let's call it "select_net", would act as a versioning value for the 
network access controls.  The existing behavior would be used when 
select_net==0 and the new behavior would be used when select_net==1; if we 
needed to introduce new checks in the future which could break compatibility 
we only enable them when select_net==2.

Thoughts?  It's not perfect, I know, but I'd like to be able to start moving 
forward with some of these labeled networking changes but the compatibility 
concerns are crippling us ...

-- 
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-08-30 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 20:02 Paul Moore [this message]
2007-08-30 20:07 ` Backwards compatibility (proposal for a new compat_net like flag) Stephen Smalley
2007-08-30 20:30   ` 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=200708301602.27272.paul.moore@hp.com \
    --to=paul.moore@hp.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.