From: Joshua Brindle <method@gentoo.org>
To: "Wightman, Reid K Civ AFRL/IFEB" <Reid.Wightman@rl.af.mil>
Cc: selinux@tycho.nsa.gov
Subject: Re: selinuxfs
Date: Tue, 13 Jun 2006 18:22:11 -0400 [thread overview]
Message-ID: <448F3A93.60203@gentoo.org> (raw)
In-Reply-To: <43055FDD054D464FA7923D0FFAF2C9C7024B1316@fsjrez02.adm.rl.af.mil>
Wightman, Reid K Civ AFRL/IFEB wrote:
>
>> I suppose a selinuxfs man page might be nice.
>> selinux-doc/README has a brief description at the end of the
>> original set of selinuxfs nodes, but hasn't been kept up to
>> date. Note that you really aren't supposed to directly
>> operate on the selinuxfs nodes - you should access them
>> indirectly via the libselinux interfaces (using helper utilities as
>> appropriate) for portability.
>>
>
> I'm tinkering with some of the libselinux functions right now and getting a
> strange error from security_compute_user(). I see that it copies data out
> of <selinuxfs>/user . On my system, this file is 0 bytes (everything is
> stock FC5, selinux status is enabled/targeted/permissive, and I just
> reloaded the policy). Is this right? How do the files here get populated?
>
>
see security/selinux/selinuxfs.c
its a pseudo filesystem like /proc which has callbacks in the kernel
when the file is read or written to.
--
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.
next prev parent reply other threads:[~2006-06-13 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 20:02 selinuxfs Wightman, Reid K Civ AFRL/IFEB
2006-06-13 22:22 ` Joshua Brindle [this message]
2006-06-14 12:06 ` selinuxfs Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2006-06-11 8:42 selinuxfs Mario Fanelli
2006-06-12 14:56 ` selinuxfs Stephen Smalley
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=448F3A93.60203@gentoo.org \
--to=method@gentoo.org \
--cc=Reid.Wightman@rl.af.mil \
--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.