Research
Skip Research Menus
Research MenuSecurity Enhanced Linux What's New Frequently Asked Questions Background Documents License Download Participating Mail List Archives Remaining Work Contributors Related Work Press Releases Information Assurance Research NIARL In-house Research Areas Mathematical Sciences Program Sabbaticals Computer & Information Sciences Research Technology Transfer Advanced Computing Advanced Mathematics Communications & Networking Information Processing Microelectronics Other Technologies Technology Fact Sheets Publications Related Links |
SELinux Mailing ListRe: [RFC & PATCH] inherited type definition.
From: Luke Kenneth Casson Leighton <lkcl_at_lkcl.net>
Date: Thu, 24 Mar 2005 22:27:54 +0000
sorry - i mis-read your question. when there are two types, it means: when you use some_macro(user) and you then declare type user_httpd_t it gets all the stuff where user_httpd_t occurs in _any_ inheritable() wrap and when you declare user_ftp_t, likewise. inheritable($1_ftp_t, $1_httpd_t) { allow A; } inheritable($1_ftp_t) { allow B; } inheritable($1_httpd_t) { allow C; } allow D; therefore: user_httpd_t comprises allow A and allow C user_ftp_t comprises allow A and allow B, user_t comprises allow A B C _and_ D. because D is not inside an inheritable() wrap, it never gets inherited by "extends" syntax. hence, this could be viewed as a simplification of having to split some_macro into ... mmm... _four (!) separate sub-macros one each covering the permissions allow A, allow B, allow C and allow D: some_macro (' some_macro_A($1) # representing inheritable A group above some_macro_B($1) # ... etc. some_macro_C($1) some_macro_D($1) ') l. -- 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.Received on Thu 24 Mar 2005 - 17:18:30 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |