From: Joshua Brindle <jbrindle@tresys.com>
To: gyurdiev@redhat.com
Cc: selinux@tycho.nsa.gov
Subject: Re: [ libsepol 0/6] Context reorganization
Date: Thu, 21 Jul 2005 14:00:07 -0400 [thread overview]
Message-ID: <42DFE2A7.9020200@tresys.com> (raw)
In-Reply-To: <1121967118.9844.17.camel@celtics.boston.redhat.com>
Ivan Gyurdiev wrote:
>The following patch moves functions relating to context_struct_t
>into file contexts.c for better organization. It makes all of
>them take policydb as argument, and enforces the sepol_ prefix.
>It uses the new debugging system. It adds a structure for
>a high level representation of a context (sepol_ctxinfo_t),
>and a new function to convert from it (sepol_context_create),
>and makes use of that function to make the conversion
>from string (formerly sepol_context_to_sid) easier.
>
>libsepol-1.1-context.diff
>
>Disclaimer 1:
>
>The following bit, as taken from the current
>policydb_context_isvalid fails for me currently. I don't
>understand the role of the cache here. Does genusers.c
>need to be modified to do something with the cache,
>when it loads the user? Do I need to correspondingly
>modify my own load_user function (which is based on genusers)?
>
>+ if (!ebitmap_get_bit(&usrdatum->cache, c->role - 1))
>+ /* user may not be associated with role */
>+ return 0;
>
>
>
The purpose of the cache is so that we don't have to do expansion of the
type sets every time we want to validate a context (since this happens
before expansion). The cache is built from policydb_index_others so if
you are't calling that it won't be built. This should work fine with an
already expanded policy since type_set_expand will just copy the type
bitmap to the cache.
--
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:[~2005-07-21 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 17:31 [ libsepol 0/6] Context reorganization Ivan Gyurdiev
2005-07-21 18:00 ` Joshua Brindle [this message]
2005-07-21 18:03 ` Ivan Gyurdiev
2005-07-21 18:09 ` Joshua Brindle
2005-07-21 18:14 ` Ivan Gyurdiev
2005-07-22 13:49 ` Ivan Gyurdiev
2005-07-22 14:03 ` Joshua Brindle
2005-07-22 14:04 ` Ivan Gyurdiev
2005-07-22 14:11 ` Joshua Brindle
2005-07-22 14:15 ` Ivan Gyurdiev
2005-07-22 14:16 ` Ivan Gyurdiev
2005-07-22 14:25 ` Joshua Brindle
2005-07-22 14:57 ` Ivan Gyurdiev
2005-07-22 15:14 ` Joshua Brindle
[not found] ` <1122386595.4470.40.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1122387393.4470.54.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1122393674.4470.73.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1122393858.2812.5.camel@celtics.boston.redhat.com>
[not found] ` <1122395431.2812.13.camel@celtics.boston.redhat.com>
[not found] ` <1122396106.4470.76.camel@moss-spartans.epoch.ncsc.mil>
2005-07-26 16:52 ` [ libsepol 10 ] Bugfixes for 0-9 Ivan Gyurdiev
2005-07-26 17:43 ` Ivan Gyurdiev
2005-07-26 19:00 ` Stephen Smalley
2005-07-26 19:01 ` Ivan Gyurdiev
2005-07-26 19:06 ` 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=42DFE2A7.9020200@tresys.com \
--to=jbrindle@tresys.com \
--cc=gyurdiev@redhat.com \
--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.