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: Why cron doesn't work in strict policy
From: Daniel J Walsh <dwalsh_at_redhat.com>
Date: Tue, 07 Feb 2006 09:34:59 -0500
Right now cron has the following code in it. if (get_security_context(pw == NULL ? "system_u" : uname, crontab_fd, &u->scontext, tabname) != 0) { free_user(u); u = NULL; goto done; }
get_security_context()
if (getseuserbyname(name, &seuser, &level) == 0) { retval=get_default_context_with_level(seuser, level, NULL, &scontext); free(seuser); free(level); if (retval) { ... Which causes cron jobs on strict policy and I would guess MLS to run at user_u since system_u is not defined and would run at level s0. -- 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:34:44 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |