Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 184592 - Shutdown command needs to be root level command
Shutdown command needs to be root level command
Product: Fedora
Classification: Fedora
Component: sysvinit (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2006-03-09 20:55 EST by Leslie Satenstein
Modified: 2014-03-16 22:58 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-10 13:47:55 EST
Type: ---
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 Leslie Satenstein 2006-03-09 20:55:16 EST
Description of problem:

Any user can do a sustem shutdown as the command is not root level protected

Version-Release number of selected component (if applicable):

core4 / core5

How reproducible:

Issue shutdown command from general or guest user

Steps to Reproduce:
Actual results:

System shuts down

Expected results:

Administrator password should be prompted for, if not root logon. That is,
shutdown should only be available from the root logon administration level. 

Additional info:
If the pc is behind a barrier, then the shutdown button is not available and the
system will not be able to suffer an unauthorized shutdown.
Comment 1 Jindrich Novy 2006-03-10 04:36:59 EST
shutdown/reboot/poweroff/halt stuff belong to SysVinit.

Please reassign back if fixing on usermode side is needed.
Comment 2 Bill Nottingham 2006-03-10 13:47:55 EST
This is normal behavior of the usermode symlinks; the console user can shut down.

You can change this behavior by editing/removing
Comment 3 David Lawrence 2007-06-21 22:10:43 EDT
Package name is now sysvinit in Fedora.

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