All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Ivan Gyurdiev <ivg2@cornell.edu>,
	SELinux List <SELinux@tycho.nsa.gov>,
	selinuxdev <selinux-dev@tresys.com>
Subject: Re: [PATCH] libsemanage/semanage - permission check for semanage
Date: Fri, 20 Jan 2006 09:04:06 -0500	[thread overview]
Message-ID: <43D0EDD6.9070501@tresys.com> (raw)
In-Reply-To: <1137766150.3648.125.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Thu, 2006-01-19 at 16:45 -0500, Joshua Brindle wrote:
> 
>>- add semanage_can_write to libsemanage which does a silent check for
>>access on the active store, modules directory and binary policy
>>directory
>>- chance semanage_is_managed to use can_write instead of create_store
>>for access check
>>- add access check to seobject.py, in semanageRecord init
> 
> 
> Also, how do you envision implementing this interface for the policy
> server backend?  Same question exists for semanage_is_managed I suppose,
> but that interface seems a little more general in concept.
>   

I wasn't at first but one could always ask the server if my context has 
write permission to the policy, which is a slightly different concept 
but from a user perspective probably means the same thing.

--
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:[~2006-01-20 14:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 21:45 [PATCH] libsemanage/semanage - permission check for semanage Joshua Brindle
2006-01-19 22:45 ` Ivan Gyurdiev
2006-01-20  1:38   ` Joshua Brindle
2006-01-20  2:11     ` Ivan Gyurdiev
2006-01-20  2:19       ` Joshua Brindle
2006-01-20 13:54 ` Stephen Smalley
2006-01-20 14:00   ` Joshua Brindle
2006-01-20 14:24     ` Stephen Smalley
2006-01-20 14:09 ` Stephen Smalley
2006-01-20 14:04   ` Joshua Brindle [this message]
2006-01-20 15:20 ` Stephen Smalley
2006-01-20 19:14   ` Joshua Brindle
2006-01-20 20:49     ` Stephen Smalley
2006-01-20 21:25       ` Joshua Brindle
2006-01-23 14:36         ` Stephen Smalley
2006-01-23 14:51           ` Joshua Brindle
2006-01-23 15:29             ` Stephen Smalley
2006-01-23 15:40               ` Joshua Brindle
2006-01-23 15:59                 ` Stephen Smalley
2006-01-23 16:05                   ` Joshua Brindle
2006-01-23 16:18                     ` Stephen Smalley
2006-01-26 20:40                       ` Joshua Brindle
2006-01-27 15:12                         ` Stephen Smalley
2006-01-27 15:17                           ` Joshua Brindle
2006-01-23 16:33                   ` Joshua Brindle

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=43D0EDD6.9070501@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=ivg2@cornell.edu \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux-dev@tresys.com \
    /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.