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: Desktop apps interoperability
From: Stephen Smalley <sds_at_tycho.nsa.gov>
Date: Mon, 28 Mar 2005 14:46:06 -0500
file_type_auto_trans() is a macro that expands to file_type_trans() and a type_transition rule specifying the default type for the new files. file_type_trans() is a macro that expands to the set of allow rules needed for the domain to create the file (including appropriate permissions to the parent directory as well as to the file). The allow rules are always needed for such a file creation to occur. The type_transition rule specifies a default in the absence of anything specified by the program via setfscreatecon(3). The ability to use setfscreatecon(3) does require that the domain have one additional permission, setfscreate, but the permission checks governing the actual file creation are the same. This is a general principle in SELinux; the same set of permission checks are applied for operations regardless of whether the type was application-specified or a default value, so that you can always determine what is permissible via the allow rules. The same is true of exec transitions for processes. The set of permission checks doesn't change; only the types involved change. -- Stephen Smalley <sds@tycho.nsa.gov> National Security Agency -- 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 Mon 28 Mar 2005 - 14:54:52 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |