From: Stephen Smalley <sds@tycho.nsa.gov>
To: Richard Haines <richard_c_haines@btinternet.com>,
"Roberts, William C" <william.c.roberts@intel.com>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: initial_sid context via libsepol
Date: Mon, 7 Mar 2016 15:32:15 -0500 [thread overview]
Message-ID: <56DDE54F.4050208@tycho.nsa.gov> (raw)
In-Reply-To: <56DDCBF6.6010605@tycho.nsa.gov>
On 03/07/2016 01:44 PM, Stephen Smalley wrote:
> On 03/07/2016 10:41 AM, Richard Haines wrote:
>>
>>
>>
>>
>>
>>> On Saturday, 5 March 2016, 14:48, Richard Haines
>>> <richard_c_haines@btinternet.com> wrote:
>>>>
>>>
>>>
>>>
>>> On Friday, 4 March 2016, 21:18, "Roberts, William C"
>>> <william.c.roberts@intel.com> wrote:
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>> How can one obtain the same value as
>>>> /sys/fs/selinux/initial_contexts/file
>>> via libsepol?
>>>>
>>>> I’ve been digging around libsepol and its not quite clear to me.
>>>>
>>>> It looks as though the record is here:
>>>> context_struct_t *a = &((policydb_t
>>> *)pol.db)->ocontexts[OCON_ISID]->context[0];
>>>> context_struct_t *b = &((policydb_t
>>> *)pol.db)->ocontexts[OCON_ISID]->context[1];
>>>>
>>>> printf("%u\n", a->type);
>>>> printf("%u\n",b->type);
>>>>
>>>> Prints:
>>>> 185
>>>> 0
>>>>
>>>> Not sure if this is right, and how to format the context struct to a
>>>> string.
>>> I didn’t see any helpers.
>>>>
>>>
>>>>
>>
>>> I've attached an example, hope it's useful
>>
>> I've updated the example with more detail and display SID name using
>> SID value not counter.
>>
>
> Any particular reason you didn't use sepol_sid_to_context()?
I guess context_to_string() on the context structure would work better
for your purposes. sepol_sid_to_context() would require loading the
sidtab via policydb_load_isids() and setting the internal policydb to
the one you loaded via sepol_set_policydb().
next prev parent reply other threads:[~2016-03-07 20:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 21:16 initial_sid context via libsepol Roberts, William C
2016-03-05 14:43 ` Richard Haines
2016-03-07 15:41 ` Richard Haines
2016-03-07 18:44 ` Stephen Smalley
2016-03-07 20:32 ` Stephen Smalley [this message]
2016-03-08 1:32 ` William Roberts
2016-03-08 13:12 ` Richard Haines
2016-03-08 13:35 ` Richard Haines
2016-03-08 13:49 ` Christopher J. PeBenito
2016-03-08 13:42 ` Stephen Smalley
2016-03-09 5:18 ` William Roberts
2016-03-09 14:09 ` Stephen Smalley
2016-03-09 15:37 ` William Roberts
2016-03-09 17:12 ` William Roberts
2016-03-09 15:42 ` Stephen Smalley
2016-03-09 15:45 ` William Roberts
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=56DDE54F.4050208@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@tycho.nsa.gov \
--cc=william.c.roberts@intel.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.