public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris PeBenito <pebenito@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] SELinux and Apache - no pid file?
Date: Thu, 06 Oct 2005 22:00:36 -0400	[thread overview]
Message-ID: <1128650436.26791.11.camel@gorn.pebenito.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0510061405510.18391@thirteen.net>

[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]

On Thu, 2005-10-06 at 14:18 -0400, Albert Lash wrote:
> The problem I am experiencing is when I restart apache. I do this as root,
> su'd from a user with SELinux role staff_r and sysadm_r. I first login via
> ssh as a normal user, then I newrole -r sysadm_r, then I su, and then I
> /etc/init.d/apache2 restart. I get a warning that there is not pid. So
> then I have to kill the process identified by ps -A, and then
> /etc/init.d/apache start. (Whenever I run an init script, I have to
> authenticate as the original user who has the sysadm_r role). The server
> starts fine, but seems to have a delay before I can access the server via
> a browser. Even when the server starts responding to browser requests, no
> pid file is written to /var/run. There aren't even any denials in the
> /var/log/messages files, which still wouldnt' prevent a pid file from
> getting written, as I am in permissive mode.

If this doesn't work in permissive, then it points to something not
SELinux related being wrong.  I suggest looking at the apache logs for
errors, and also check DAC perms.

> I have also tried the SELinux run_init command before the ini script with
> the same results.

This won't help because Gentoo already has run_init integrated into the
init script system.

> Is this standard behavior for Apache2 on SELinux?

No, I can't reproduce it on my enforcing systems.

-- 
Chris PeBenito
<pebenito@gentoo.org>
Developer,
Hardened Gentoo Linux
Embedded Gentoo Linux
 
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243
Key fingerprint = B0E6 877A 883F A57A 8E6A  CB00 BC8E E42D E6AF 9243


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-10-07  2:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 19:37 [gentoo-hardened] gcc-config Albert Lash
2005-09-24 22:39 ` Albert Lash
2005-09-25 11:44   ` [gentoo-hardened] gcc-hardened Albert Lash
2005-09-25 21:37     ` Chris PeBenito
2005-10-06 18:18   ` [gentoo-hardened] SELinux and Apache - no pid file? Albert Lash
2005-10-07  2:00     ` Chris PeBenito [this message]
2005-10-07  2:25       ` Travis Fraser
2005-10-07 12:41         ` Albert Lash
2005-10-15 15:40           ` [gentoo-hardened] AMD64 sys-libs/ss Albert Lash
2005-10-15 17:40             ` Chris PeBenito

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=1128650436.26791.11.camel@gorn.pebenito.net \
    --to=pebenito@gentoo.org \
    --cc=gentoo-hardened@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox