Security 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: dynamic context transitions
From: Luke Kenneth Casson Leighton <lkcl_at_lkcl.net>
Date: Mon, 1 Nov 2004 14:10:26 +0000
... where in those domains there may or may not be the permission to make a transition. SO. this proposal is a little bit like seteuid-for-selinux, only not really, because seteuid has the ability to switch to any uid and then to any uid after that, ad infinitum. i wonder if it would help at all with samba's predicament? would it be possible to use this to have an smbd process transition to a user-based-file-access-only-context and then back-to-"root-like"-with-no-file-access-allowed? reminder: samba's predicament is that processes on a per-computer basis tend not to die, plus they can be heavily reused (particularly in Terminal Server situations) where one TCP connection to one smbd process manages several multiplexed user requests with _totally_ different user contexts. [yes i know samba is badly designed in this respect: it REALLY needs a threaded or threaded-like architecture: a threaded client application gets given a single server-side process for its remote file access, which results ultimately in client-side thread blocking - but leaving that aside] and also would it be possible to use this proposal to track what famd does, too? [reminder: famd doesn't spawn per-user processes to see what files need monitoring on a per-user basis, it uses seteuid instead, just like samba (or maybe setfsuid)].
not that my opinion has any weight in
whether said application design is any _good_ - samba's single-blocking-server-process serving multiple-threaded-multiple-user-context-clients multiplexed onto a single TCP connection being a notable example - is debatable. 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 Mon 1 Nov 2004 - 08:59:43 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |