From: Stephen Smalley <sds@tycho.nsa.gov>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: Joshua Brindle <brindle@quarksecurity.com>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: Find attributes for a type with sepol
Date: Tue, 29 Sep 2015 17:04:53 -0400 [thread overview]
Message-ID: <560AFCF5.6050900@tycho.nsa.gov> (raw)
In-Reply-To: <CAFftDdqM_FG1gmXNiuALiguMWe2fam+T03qSO=8Q67XCp+eFqg@mail.gmail.com>
On 09/29/2015 04:51 PM, William Roberts wrote:
>
>
> On Tue, Sep 29, 2015 at 1:25 PM, Stephen Smalley <sds@tycho.nsa.gov
> <mailto:sds@tycho.nsa.gov>> wrote:
>
> On 09/29/2015 04:19 PM, William Roberts wrote:
>
> So is this information only available at compile time? I see
> that the
> types field is
> empty for both attributes and types. Perhaps my code is wrong to do
> this, but
> I can loop over the ebitmap entries from the attr_type and type_attr
> maps just
> fine.
>
>
> Yes, it is discarded from the binary policy, which instead has
> type_attr_map and attr_type_map.
>
> According to a comment in the struct attr_type_map is discarded as well,
> which would make sense
> given that the per-attribute type map is thrown away as well.
>
> aosp/external/selinux/libsepol/include/sepol$ grep -rn 'attr_type_map' *
> policydb/policydb.h:575:ebitmap_t *attr_type_map;/* not saved in the
> binary policy */
It is re-created on load; see policydb_read(). So it is always
available to you.
prev parent reply other threads:[~2015-09-29 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 22:39 Find attributes for a type with sepol Roberts, William C
2015-09-24 12:43 ` James Carter
2015-09-24 12:59 ` Stephen Smalley
2015-09-24 13:58 ` Joshua Brindle
2015-09-29 18:15 ` William Roberts
2015-09-29 19:11 ` Joshua Brindle
2015-09-29 19:33 ` William Roberts
2015-09-29 19:35 ` Joshua Brindle
2015-09-29 19:36 ` William Roberts
2015-09-29 20:19 ` William Roberts
2015-09-29 20:25 ` Stephen Smalley
2015-09-29 20:51 ` William Roberts
2015-09-29 21:04 ` Stephen Smalley [this message]
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=560AFCF5.6050900@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=bill.c.roberts@gmail.com \
--cc=brindle@quarksecurity.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.