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: named SELinux policy
From: Ivan Gyurdiev <ivg2_at_cornell.edu>
Date: Mon, 06 Mar 2006 13:12:24 -0500
> File context that differs from parent directory is especially hard to Should automatic type transitions be treated as a hack, placed there until the app starts using setfscreatecon? Should they instead be treated as the way to do things, with applications being modified to better organize their files into folders, and the folders pre-created as appropriate. Automated transitions have already proved difficult when mixing files of different types in the same folder, and also with shared libraries creating files. It seems like the app has much more knowledge about the file than the kernel's (src_context, target_class) pair. However, should we be incorporating selinux contexts into applications [ as is already done in consolehelper ]? How reliable are those context? The rwx of chmod() are pretty much set in stone. Policy changes all the time. Is it better to keep selinux logic out of applications instead? -- 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 6 Mar 2006 - 13:12:33 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |