From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Valdis.Kletnieks@vt.edu, russell@coker.com.au,
James Morris <jmorris@redhat.com>,
selinux@tycho.nsa.gov
Subject: Re: [RFC][PATCH 0/3] Reduce number of avtab nodes
Date: Thu, 04 Aug 2005 11:52:05 -0400 [thread overview]
Message-ID: <42F239A5.10408@tresys.com> (raw)
In-Reply-To: <1123170310.13654.64.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Thu, 2005-08-04 at 11:38 -0400, Joshua Brindle wrote:
>
>
>>But just incase (also mentioned in a previous email), would it be
>>possible to use a macro in the kernel to switch between 16 and 32 bit
>>avtab keys in the kernel and then make checkpolicy write a "fat" policy
>>if the types exceed 16 bits? This would allow the possibility of having
>>a huge number of types without penalizing all users.
>>
>>
>
>I don't think we want a kernel config option altering the expected
>binary policy format. That would also mean that /selinux/policyvers ==
>n could have two meanings depending on how the kernel was configured,
>leaving userspace rather confused about what to provide it.
>
>
This is exactly what the old MLS system did right? I suppose that was
removed and for the better...
So, why not add a value size table to the header of the policy? I know
this makes reads (and writes) a real pain but some cleaver unions could
make that easier :)
Anyway, it's just a suggestion, I honestly don't know if it will ever be
needed but I believe that it's much better to keep the smaller fields
since the vast majority of the cases will benefit from it and only
radical corner cases would be affected.
--
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-08-04 15:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 16:49 [RFC][PATCH 0/3] Reduce number of avtab nodes Stephen Smalley
2005-07-29 17:16 ` [RFC][PATCH 1/3] " Stephen Smalley
2005-07-29 17:22 ` [RFC][PATCH 2/3] " Stephen Smalley
2005-07-29 17:23 ` [RFC][PATCH 3/3] " Stephen Smalley
2005-07-29 18:01 ` [RFC][PATCH 0/3] " Stephen Smalley
2005-07-29 19:05 ` James Morris
2005-07-30 4:20 ` James Morris
2005-07-30 19:13 ` Joshua Brindle
2005-07-31 15:59 ` James Morris
2005-08-01 13:41 ` Stephen Smalley
2005-08-01 14:22 ` Luke Kenneth Casson Leighton
2005-08-01 14:58 ` Joshua Brindle
2005-08-01 15:04 ` Stephen Smalley
2005-08-01 15:09 ` Stephen Smalley
2005-08-01 15:32 ` Joshua Brindle
2005-08-04 7:57 ` Russell Coker
2005-08-04 14:35 ` Valdis.Kletnieks
2005-08-04 14:38 ` Stephen Smalley
2005-08-04 15:38 ` Joshua Brindle
2005-08-04 15:45 ` Stephen Smalley
2005-08-04 15:52 ` Joshua Brindle [this message]
2005-08-04 15:46 ` Russell Coker
2005-08-02 16:43 ` Stephen Smalley
2005-08-02 20:50 ` Stephen Smalley
2005-08-04 12:52 ` Stephen Smalley
2005-08-04 16:14 ` Stephen Smalley
2005-08-08 18:42 ` Stephen Smalley
2005-08-04 7:42 ` Russell Coker
2005-08-04 13:25 ` 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=42F239A5.10408@tresys.com \
--to=jbrindle@tresys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jmorris@redhat.com \
--cc=russell@coker.com.au \
--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.