Bug 971606 - 'service httpd status' doesn't run as non root _and_ returns incorrect status
'service httpd status' doesn't run as non root _and_ returns incorrect status
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: pre-dev-freeze
: 6.6
Assigned To: Web Stack Team
BaseOS QE Security Team
Depends On:
Blocks: 980134
  Show dependency treegraph
Reported: 2013-06-06 18:16 EDT by Pádraig Brady
Modified: 2016-01-04 09:47 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 980134 (view as bug list)
Last Closed: 2013-07-01 09:28:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pádraig Brady 2013-06-06 18:16:55 EDT
There are two closely related issues here:

I would expect this command to succeed as a non root user?

  $ service httpd status
  httpd dead but subsys locked

If that's not possible fair enough.
But the issue is compounded by...

...the init script return code is incorrect:

  $ echo $?

states that "2" means the service is dead.
In this case "4" should be returned so that status
for this service can be presented correctly.
Comment 1 Jan Kaluža 2013-06-07 00:50:23 EDT
I have checked httpd initscript and it uses "status" function from /etc/rc.d/init.d/functions (from package "initscripts") and returns its return code.

This function checks if the /var/run/httpd/httpd.pid exists, but /var/run/httpd directory has mode 0710, so as a user, you are not allowed to read its content. status function in /etc/init.d/functions should probably check for this case and return 4. I think this should be filed as a bug against initscripts package.

I will ask Joe Orton, if it's possible change the /var/run/httpd permissions to allow users reading the PID file. I don't see any reason why not to do that (and lot of daemons do that), but maybe I'm missing something...
Comment 2 Joe Orton 2013-06-10 04:13:41 EDT
We put other stuff in /var/run/httpd - AF_UNIX sockets notably (mod_cgid, mod_wsgi, etc).  I'm not sure it's a actively harmful... do we guarantee that the status command works as non-root?  What do the SELinux rules enforce?
Comment 3 Joe Orton 2013-07-01 09:28:37 EDT
Lacking any strong motivation I don't think we should change this.  I don't think we could or should guarantee that the "status" command will work properly for non-root users in all cases; there may well be many exceptional cases which we couldn't anticipate.  systemd addresses this issue properly.

Note You need to log in before you can comment on or make changes to this bug.