From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: "R. Steven Rainwater" <srainwater@ncc.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: dumb newbie questions
Date: Mon, 20 Jun 2005 20:05:07 +0100 [thread overview]
Message-ID: <20050620190507.GD8451@lkcl.net> (raw)
In-Reply-To: <1119281369.30000.56.camel@rodan.ncc.com>
On Mon, Jun 20, 2005 at 10:29:29AM -0500, R. Steven Rainwater wrote:
> What can I say, I chose the subject line for a reason... :-)
:)
use ls -Z a _lot_.
then go through the file named file_contexts checking the
regexps to make sure that the file context you see with
ls -Z matches one of the regexps you see in the file_contexts
file.
if it don't look like it's correct (because you did a mv rather than cp
with the option to set the file context when the file is in its new
location) then do a restorecon.
but most critically, remember that only certain areas have been
"allocated" as suitable areas for cgi-scripts.
look in httpd.fc (or is it apache.fc) to see what those areas are.
you will expect to see a line like:
/var/www/cgi-bin/* -- httpd_cgi_exec_t
which means that anything executed from /var/www/cgi-bin/
will be given an selinux context of httpd_cgi_exec_t.
[... but remember what i said above about file_contexts: if you then put
files _into_ /var/www/cgi-bin/ you must double check that (in this
case) they have (e.g.) a context of httpd_cgi_exec_t (by using ls -Z)
and if they _don't_ then you _must_ do restorecon
/var...../mynewscript.
]
so.
if you just blop files into /var/www/my-home-grown-cgi-server-directory
and then don't also modify httpd.fc to reflect this new location
(with an appropriate regexp) then no amount of restorecon'ing will
help you.
hope this helps.
l.
--
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:[~2005-06-20 19:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 20:01 SELinux Integrated Logging Tool Brandon Pollet
2005-06-17 23:43 ` James Morris
2005-06-18 15:39 ` Steve G
2005-06-18 23:38 ` dumb newbie questions R. Steven Rainwater
2005-06-19 6:45 ` Ivan Gyurdiev
2005-06-19 16:40 ` Casey Schaufler
2005-06-19 19:51 ` Ivan Gyurdiev
2005-06-19 20:14 ` Casey Schaufler
2005-06-19 20:57 ` Ivan Gyurdiev
2005-06-19 21:31 ` Casey Schaufler
2005-06-19 22:10 ` Luke Kenneth Casson Leighton
2005-06-20 0:28 ` Casey Schaufler
2005-06-19 22:13 ` Luke Kenneth Casson Leighton
2005-06-20 0:16 ` Casey Schaufler
2005-06-20 19:21 ` Luke Kenneth Casson Leighton
2005-06-20 20:41 ` Casey Schaufler
2005-06-20 21:01 ` Valdis.Kletnieks
2005-06-20 21:36 ` Casey Schaufler
2005-06-22 9:48 ` Christopher Warner
2005-06-19 20:41 ` Ivan Gyurdiev
2005-06-20 3:34 ` R. Steven Rainwater
2005-06-20 4:45 ` Valdis.Kletnieks
2005-06-20 14:45 ` R. Steven Rainwater
2005-06-20 15:14 ` Ivan Gyurdiev
2005-06-20 15:29 ` R. Steven Rainwater
2005-06-20 15:44 ` Ivan Gyurdiev
2005-06-20 16:40 ` R. Steven Rainwater
2005-06-20 16:59 ` Ivan Gyurdiev
2005-06-20 17:35 ` Karl MacMillan
2005-06-20 18:06 ` R. Steven Rainwater
2005-06-20 18:18 ` Daniel J Walsh
2005-06-24 6:22 ` Russell Coker
2005-06-20 18:06 ` Daniel J Walsh
2005-06-20 18:57 ` Luke Kenneth Casson Leighton
2005-06-20 15:56 ` Stephen Smalley
2005-06-20 19:05 ` Luke Kenneth Casson Leighton [this message]
2005-06-20 16:28 ` Stephen Smalley
2005-06-20 18:49 ` Luke Kenneth Casson Leighton
2005-06-19 22:17 ` Luke Kenneth Casson Leighton
2005-06-20 4:11 ` Ivan Gyurdiev
2005-06-20 13:12 ` Trevor Vaughan
2005-06-20 15:21 ` R. Steven Rainwater
2005-06-20 15:40 ` Ivan Gyurdiev
2005-06-20 16:20 ` Stephen Smalley
2005-06-30 22:11 ` cgiemail and senmail policy R. Steven Rainwater
2005-07-03 14:21 ` 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=20050620190507.GD8451@lkcl.net \
--to=lkcl@lkcl.net \
--cc=SELinux@tycho.nsa.gov \
--cc=srainwater@ncc.com \
/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.