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: mysql policy
From: Tom <tom_at_lemuria.org>
Date: Wed, 30 Oct 2002 10:35:22 +0100
I'm asking because I have largely tossed Russell's mysqld domain and started a new one from scratch, not because Russell's was in any way bad but because doing so allows me to better understand what is happening and what permissions it needs. This way I found out that the wrapper (safe_mysqld) that the init script uses to start mysqld requires some more and other permissions than the daemon itself, so I'm thinking about putting it into a different domain so that the daemon, once running, doesn't have all those unneeded priviledges. safe_mysqld is a shell script. I can't see a problem with that from the pure "hacking" perspective (modifying a shell script is not that much easier than modifying a binary), but maybe its reliance on /bin/sh makes it a different game?
-- Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
-- |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |