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: Why cron doesn't work in strict policy
From: Ivan Gyurdiev <ivg2_at_cornell.edu>
Date: Tue, 07 Feb 2006 09:40:05 -0500
>>> cron ---> getseuserbyname(system_u) >> So for using system cronfiles, the getseuserbyname() call needs to be >> skilled (since you've already decided on the user - system_u, user.c: >> line 87). Not sure about level. Alternatively you can query using root. > Seems to me we have two choices. One is to change cron to default to > "root" when there is no username or to add system_u to the seusers file.Well, on second thought querying root is not going to get you system_u in any way... I think the seuser query just needs to be skipped if you've decided to use system_u. -- 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 Tue 7 Feb 2006 - 09:40:21 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |