All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Anderson <mra@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Darrel Goeddel <dgoeddel@TrustedCS.com>, selinux@tycho.nsa.gov
Subject: Re: context_sensitivity_{get|set}
Date: Fri, 13 Oct 2006 12:21:12 -0400	[thread overview]
Message-ID: <452FBCF8.2060805@hp.com> (raw)
In-Reply-To: <1160748247.14346.26.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Thu, 2006-10-12 at 15:19 -0400, Matt Anderson wrote:
>>For my latest CUPS patch I needed to include code that set the
>>sensitivity of the spool file storing the to that of the client's
>>context when they queued the job.  I used context_range_get() to
>>retrieve the MLS range, but then had to use strtok() to get the lower bound.
>>
>>Is context_sensitivity_get() or context_sensitivity_set() a function
>>that other consumers might need?  Should it be included in libselinux?
> 
> Providing functions to get/set the low and high would make sense (and
> newrole already has to do similar processing internally for newrole -l),
> but I don't follow the function names above - do you want just the low
> sensitivity (i.e. no categories) or the entire low level?  And you need
> to indicate whether you are operating on the low or the high levels in
> the interface.
> 

I agree names are a bit confusing, I was at a loss for what to call them
myself and decided to defer to the output from secon:

# secon
user: root
role: staff_r
type: staff_t
sensitivity: SystemLow
clearance: SystemHigh
mls-range: SystemLow-SystemHigh

For my usage I need the entire low level.  There may be other users want
just the sensitivity, but I'd be concerned that information would be
unintentionally downgraded by leaving off categories.

-matt

--
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:[~2006-10-13 16:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 19:19 context_sensitivity_{get|set} Matt Anderson
2006-10-13 14:04 ` context_sensitivity_{get|set} Stephen Smalley
2006-10-13 15:47   ` context_sensitivity_{get|set} Klaus Weidner
2006-10-13 16:18     ` context_sensitivity_{get|set} Paul Moore
2006-10-13 16:26       ` context_sensitivity_{get|set} Paul Moore
2006-10-13 17:24         ` context_sensitivity_{get|set} Klaus Weidner
2006-10-13 16:32       ` context_sensitivity_{get|set} Stephen Smalley
2006-10-13 16:21   ` Matt Anderson [this message]
2006-10-13 16:40     ` context_sensitivity_{get|set} Stephen Smalley
2006-10-13 20:36       ` context_sensitivity_{get|set} Linda Knippers
2006-10-13 20:54         ` context_sensitivity_{get|set} Stephen Smalley
2006-10-13 16:58     ` context_sensitivity_{get|set} Casey Schaufler
2006-10-13 18:47       ` context_sensitivity_{get|set} Stephen Smalley
2006-10-13 19:43         ` context_sensitivity_{get|set} Casey Schaufler
2006-10-13 20:03           ` context_sensitivity_{get|set} Stephen Smalley
2006-10-13 21:38             ` context_sensitivity_{get|set} Casey Schaufler
2006-10-13 22:06               ` context_sensitivity_{get|set} Joe Nall

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=452FBCF8.2060805@hp.com \
    --to=mra@hp.com \
    --cc=dgoeddel@TrustedCS.com \
    --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.