From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Why cron doesn't work in strict policy
Date: Tue, 07 Feb 2006 09:42:56 -0500 [thread overview]
Message-ID: <43E8B1F0.5030208@cornell.edu> (raw)
In-Reply-To: <1139323414.2872.46.camel@moss-spartans.epoch.ncsc.mil>
>> 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.
--
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.
next prev parent reply other threads:[~2006-02-07 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43E7C52E.601@cornell.edu>
[not found] ` <43E7C804.3040507@cornell.edu>
2006-02-07 14:34 ` Why cron doesn't work in strict policy Daniel J Walsh
2006-02-07 14:40 ` Ivan Gyurdiev
2006-02-07 14:43 ` Stephen Smalley
2006-02-07 14:40 ` Daniel J Walsh
2006-02-07 14:42 ` Ivan Gyurdiev [this message]
2006-02-07 14:55 ` Stephen Smalley
2006-02-07 15:02 ` Ivan Gyurdiev
2006-02-07 15:23 ` Daniel J Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E8B1F0.5030208@cornell.edu \
--to=ivg2@cornell.edu \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.