All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	selinux@tycho.nsa.gov, jmorris@namei.org
Subject: Re: [PATCH 4/4] SELinux: allow userspace to read policy back out of the kernel
Date: Tue, 15 Jun 2010 10:33:09 -0400	[thread overview]
Message-ID: <1276612389.2749.38.camel@localhost> (raw)
In-Reply-To: <4C17049D.6090106@schaufler-ca.com>

On Mon, 2010-06-14 at 21:42 -0700, Casey Schaufler wrote:
> Eric Paris wrote:
> > On Mon, 2010-06-14 at 10:48 -0400, Stephen Smalley wrote:
> >   
> >> On Fri, 2010-06-11 at 12:37 -0400, Eric Paris wrote:
> >>     
> >>> There is interest in being able to see what the actual policy is that was
> >>> loaded into the kernel.  The patch creates a new selinuxfs file
> >>> /selinux/policy which can be read by userspace.  The actual policy that is
> >>> loaded into the kernel will be written back out to userspace.
> >>>       
> >> Why a new node vs a read op for /selinux/load?
> >>     
> >
> > No reason why I couldn't.  Just 'load' seemed to imply a connotation
> > which wasn't appropriate.  If you prefer I'll switch it when I do
> > another version.
> >   
> 
> If it makes any difference Smack /smack/load does read as well as write.
> You have the opportunity to make 2 or 3 users less confused if you do
> things consistently. After all, Smack uses load because SELinux does,
> the name is actually arbitrary, and why do something differently when
> it doesn't really matter?

I did two things yesterday.  First I switch the read
from /selinux/policy to /selinux/load.  Then I undid that change and
started generating the in kernel policy buffer on open() rather than on
read().  It allowed me to use cat /etc/policy > policy rather than using
my own half ass hacked utility.  The reason I undid the policy->load
change was because I didn't really want to store the old policy on open
if they were going to write() a new policy.  I can probably make the
determination based on the f_mode, but didn't really play with it yet.
I  try to do both in the next go-round.

I'm still trying to figure out what I did to make malformed policies.
Must have screwed something up ripping out my prink's and debug hooks,
because it isn't working for me now either....

Unrelated note, can we take patches 1,2,3 ?  They are just cleanups....

-Eric


--
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:[~2010-06-15 14:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 16:37 [PATCH 1/4] SELinux: seperate range transition rules to a seperate function Eric Paris
2010-06-11 16:37 ` [PATCH 2/4] SELinux: move genfs read to a separate function Eric Paris
2010-06-16 14:18   ` Stephen Smalley
2010-06-16 14:24     ` Stephen Smalley
2010-06-11 16:37 ` [PATCH 3/4] SELinux: break ocontext reading into " Eric Paris
2010-06-16 14:39   ` Stephen Smalley
2010-06-11 16:37 ` [PATCH 4/4] SELinux: allow userspace to read policy back out of the kernel Eric Paris
2010-06-14 14:48   ` Stephen Smalley
2010-06-14 15:12     ` Eric Paris
2010-06-15  4:42       ` Casey Schaufler
2010-06-15 14:33         ` Eric Paris [this message]
2010-06-16 14:53           ` Stephen Smalley
2010-06-16 15:26             ` Eric Paris
2010-06-16 16:41               ` Stephen Smalley
2010-06-16 16:58                 ` Eric Paris
2010-06-17  7:26             ` KaiGai Kohei
2010-06-17 14:51               ` Eric Paris
2010-06-14 14:57   ` Stephen Smalley
2010-06-14 14:59     ` Stephen Smalley
2010-06-14 15:24     ` Eric Paris
2010-06-14 16:14       ` Stephen Smalley
2010-06-14 17:55         ` Eric Paris
2010-06-14 18:04           ` Stephen Smalley
2010-06-18 12:01           ` Christopher J. PeBenito
2010-06-16 13:02 ` [PATCH 1/4] SELinux: seperate range transition rules to a seperate function Stephen Smalley
2010-06-17  5:02 ` James Morris

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=1276612389.2749.38.camel@localhost \
    --to=eparis@redhat.com \
    --cc=casey@schaufler-ca.com \
    --cc=jmorris@namei.org \
    --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.