From: Scott Cain <cain@cshl.org>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: FC3, Apache and CGI web app
Date: Thu, 03 Feb 2005 11:57:32 -0500 [thread overview]
Message-ID: <1107449853.3300.5.camel@localhost.localdomain> (raw)
In-Reply-To: <42024D2F.1040806@redhat.com>
Dan,
I did the relabel/reboot and was able to change the context, now my next
question: was changing the context of the GBrowse tmp directory supposed
to allow it to run with SELinux enabled for httpd? ie:
httpd_disable_trans=0
httpd_enable_cgi=1
httpd_enable_homedirs=1
httpd_ssi_exec=1
httpd_tty_comm=1
httpd_unified=1
Because it doesn't; I'm back to 500 errors. Is what you meant instead
that I have to change the context and make it writable only by the owner
(ie, apache)?
Thanks for your patience,
Scott
On Thu, 2005-02-03 at 11:11 -0500, Daniel J Walsh wrote:
> Scott Cain wrote:
>
> >OK, now I get this:
> >
> >[scott@localhost gbrowse]$ sudo chcon -R -t httpd_sys_content_t /var/www/html/gbrowse/tmp
> >/usr/bin/chcon: can't apply partial context to unlabeled file /var/www/html/gbrowse/tmp/yeast_chr1
> >
> >
> >
> Has this machine been labeled or booted with selinux=0? You need to
> relabel the system.
>
> touch /.autorelabel
> reboot
>
>
> >About my comment about the man page: I was just saying that it doesn't
> >say much about what options are available (like how would I know I need
> >to use 'httpd_sys_content_t'?) I'm guessing this is further documented
> >somewhere else.
> >
> >Thanks,
> >Scott
> >
> >On Thu, 2005-02-03 at 10:59 -0500, Daniel J Walsh wrote:
> >
> >
> >>Scott Cain wrote:
> >>
> >>
> >>
> >>>On Thu, 2005-02-03 at 10:35 -0500, Daniel J Walsh wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>No but you could just change the context of tmp to httpd_sys_content_t
> >>>>
> >>>>chcon -R httpd_sys_content_t /var/www/html/gbrowse/tmp
> >>>>
> >>>>Which should fix it.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>[scott@localhost gbrowse]$ sudo chcon -R httpd_sys_content_t /var/www/html/gbrowse/tmp
> >>>/usr/bin/chcon: invalid context: httpd_sys_content_t
> >>>
> >>>Is there a typo in there somewhere? Also, is this documented somewhere?
> >>>`man` and `info` are particularly terse and not very helpful.
> >>>
> >>>Thanks,
> >>>Scott
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>Oops
> >>chcon -R -t httpd_sys_content_t /var/www/html/gbrowse/tmp
> >>
> >>There should be a man page, there is one on my machine
> >>
> >>
> >>plain text document attachment (chcon)
> >>CHCON(1) User Commands CHCON(1)
> >>
> >>
> >>
> >>NAME
> >> chcon - change security context
> >>
> >>SYNOPSIS
> >> chcon [OPTION]... CONTEXT FILE...
> >> chcon [OPTION]... --reference=RFILE FILE...
> >>
> >>DESCRIPTION
> >> Change the security context of each FILE to CONTEXT.
> >>
> >> -c, --changes
> >> like verbose but report only when a change is made
> >>
> >> -h, --no-dereference
> >> affect symbolic links instead of any referenced file (available
> >> only on systems with lchown system call)
> >>
> >> -f, --silent, --quiet
> >> suppress most error messages
> >>
> >> -l, --range
> >> set range RANGE in the target security context
> >>
> >> --reference=RFILE
> >> use RFILE’s context instead of using a CONTEXT value
> >>
> >> -R, --recursive
> >> change files and directories recursively
> >>
> >> -r, --role
> >> set role ROLE in the target security context
> >>
> >> -t, --type
> >> set type TYPE in the target security context
> >>
> >> -u, --user
> >> set user USER in the target security context
> >>
> >> -v, --verbose
> >> output a diagnostic for every file processed
> >>
> >> --help display this help and exit
> >>
> >> --version
> >> output version information and exit
> >>
> >>REPORTING BUGS
> >> Report bugs to <email@host.com>.
> >>
> >>SEE ALSO
> >> The full documentation for chcon is maintained as a Texinfo manual.
> >> If the info and chcon programs are properly installed at your site,
> >> the command
> >>
> >> info chcon
> >>
> >> should give you access to the complete manual.
> >>
> >>
> >>
> >>chcon (coreutils) 5.0 July 2003 CHCON(1)
> >>
> >>
>
>
--
------------------------------------------------------------------------
Scott Cain, Ph. D. cain@cshl.org
GMOD Coordinator (http://www.gmod.org/) 216-392-3087
Cold Spring Harbor Laboratory
--
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-02-03 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 21:07 FC3, Apache and CGI web app Scott Cain
2005-02-02 23:46 ` Daniel J Walsh
2005-02-03 4:30 ` Scott Cain
2005-02-03 14:51 ` Daniel J Walsh
2005-02-03 15:25 ` Scott Cain
2005-02-03 15:35 ` Daniel J Walsh
2005-02-03 15:48 ` Scott Cain
2005-02-03 15:52 ` Stephen Smalley
2005-02-03 15:59 ` Daniel J Walsh
2005-02-03 16:01 ` Scott Cain
2005-02-03 16:11 ` Daniel J Walsh
2005-02-03 16:57 ` Scott Cain [this message]
2005-02-03 3:01 ` Colin Walters
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=1107449853.3300.5.camel@localhost.localdomain \
--to=cain@cshl.org \
--cc=dwalsh@redhat.com \
--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.