All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Pascal Hahn <p.hahn@laufwerka.de>
Cc: SELinux@tycho.nsa.gov
Subject: Re: apache rule to make it write in directory
Date: Fri, 25 Jun 2004 00:32:49 +1000	[thread overview]
Message-ID: <200406250032.49303.russell@coker.com.au> (raw)
In-Reply-To: <40DACAF8.6000308@laufwerka.de>

On Thu, 24 Jun 2004 22:37, Pascal Hahn <p.hahn@laufwerka.de> wrote:
> I got the problem that my apache2 under selinux running on gentoo linux is
> not able to write to a certain directory under htdocs which i need to be
> writable.
>
> I need a rule to make it write in that directory but didnt find a
> possibility to do so by now.
>
> Perhaps someone can help me out here.

Please show us the AVC messages from the access that is denied and then it 
should be easy to demonstrate how to customise the policy to do what you 
require.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

--
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.

  reply	other threads:[~2004-06-24 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 12:37 apache rule to make it write in directory Pascal Hahn
2004-06-24 14:32 ` Russell Coker [this message]
2004-06-25  6:35   ` Pascal Hahn
2004-06-25  7:51     ` Russell Coker
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30 10:24 Pascal Hahn
2004-06-30 10:41 Pascal Hahn
2004-06-30 14:27 ` Russell Coker
2004-07-01 11:32   ` Pascal Hahn

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=200406250032.49303.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=SELinux@tycho.nsa.gov \
    --cc=p.hahn@laufwerka.de \
    /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.