Research Menu

.
Skip Search Box

SELinux Mailing List

Re: Why cron doesn't work in strict policy

From: Stephen Smalley <sds_at_tycho.nsa.gov>
Date: Tue, 07 Feb 2006 09:55:41 -0500


On Tue, 2006-02-07 at 09:42 -0500, Ivan Gyurdiev wrote:
> >> 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.
> >>
> >
> > We should add system_u to seusers.
> >
> Why? There's no such Linux user...
> This will cause problems with genhomedircon.

What kind of problem? Other alternative is to have crond skip the getseuserbyname() lookup if dealing with a system cron job (indicated by use of system_u), which just means a special cased check in the crond code.

-- 
Stephen Smalley
National Security Agency


--
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:50:01 EST
 

Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009

 
bottom

National Security Agency / Central Security Service