All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: Christian Kuester <c.kuester@tarent.de>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: Adding local nodecon's through semanage
Date: Tue, 08 Jul 2008 11:14:57 -0400	[thread overview]
Message-ID: <48738471.50701@manicmethod.com> (raw)
In-Reply-To: <48733DCF.3000808@tarent.de>

Christian Kuester wrote:
> Stephen Smalley schrieb:
>>> [ netmask semantic in nodecon ]
>> Ok, this isn't actually a bug in the code at all.
> 
> I see. Thanks for clearing that up for me!
> 
>> Arguably semanage and checkpolicy should apply the mask to the address
>> as a precaution against misconfiguration by the user.  That's easy
>> enough to do.
>>
>> Other tidbits on the semanage patch that I noticed:
>> - semanage node -l was broken, requires additional argument that has
>> been added to the list methods subsequently.  Also would be nice to
>> support locallist/-C option.
>> - semanage node -p option should take a string rather than an integer
>> and map it to the proper symbolic constant for ipv4/ipv6.
>> The ordering issue is a red herring at least for this example as the
>> sort is only applied to the local entries, and then they are merged to
>> the front of the policy-provided definitions.  Which may become an issue
>> down the road particularly if we move object contexts to modules. 
> 
> I think I could do the changes to at least the semanage code, if there
> is still interest in it.
> 
> But I must admit, that my understanding of the "ordering issue" is quiet
> limited and my list research on an explaination was unsuccessful so far.
> Is this a blocker for general semanage support of nodecons?
> 

The ordering issue only comes up when you have overlapping masks. This may not be an issue in practice though, I suppose we'll see.


--
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:[~2008-07-08 15:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 13:47 Adding local nodecon's through semanage Christian Kuester
2008-07-03 14:32 ` Paul Moore
2008-07-03 16:16   ` Stephen Smalley
2008-07-03 16:45     ` Paul Moore
2008-07-03 17:01       ` Stephen Smalley
2008-07-04  8:10         ` Christian Kuester
2008-07-07 17:11 ` Stephen Smalley
2008-07-08 10:13   ` Christian Kuester
2008-07-08 12:30     ` Stephen Smalley
2008-07-29 12:13       ` Stephen Smalley
2008-08-14  7:32         ` [PATCH] Revised Patch for local nodecon support in semanage (was: Adding local nodecon's through semanage) Christian Kuester
2008-08-21 20:59           ` Stephen Smalley
2008-08-26 13:37             ` Stephen Smalley
2008-07-08 15:14     ` Joshua Brindle [this message]

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=48738471.50701@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=c.kuester@tarent.de \
    --cc=sds@tycho.nsa.gov \
    --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.