From owner-freebsd-hackers  Sun Oct 29 21:29:18 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA04328
          for hackers-outgoing; Sun, 29 Oct 1995 21:29:18 -0800
Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA04318
          for <freebsd-hackers@freebsd.org>; Sun, 29 Oct 1995 21:29:08 -0800
Received: from localhost (localhost [127.0.0.1])
	  by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id FAA02874
	  ; Mon, 30 Oct 1995 05:17:27 GMT
To: Charles Henrich <henrich@crh.cl.msu.edu>
cc: freebsd-hackers@freebsd.org
Subject: Re: Why cant a setuid process do a shutdown? 
In-reply-to: Your message of "Sun, 29 Oct 1995 17:45:54 EST."
             <199510292245.RAA05648@crh.cl.msu.edu> 
Date: Mon, 30 Oct 1995 05:17:25 +0000
Message-ID: <2872.815030245@palmer.demon.co.uk>
From: Gary Palmer <gary@palmer.demon.co.uk>
Sender: owner-hackers@freebsd.org
Precedence: bulk

Charles Henrich stands accused of writing in message ID
<199510292245.RAA05648@crh.cl.msu.edu>:
>Okay, I've tried everything, and I cant figure out anyway in which a setuid
>process can execute a shutdown.

gary@palmer:~> ls -alo `where shutdown`
-r-sr-x---  1 root  operator  - 126976 Nov 22  1994 /sbin/shutdown

Works fine for me (my normal UID is in the operator group. I did this
as I really hated su'ing to root just to switch my machine off for the
night...)

(and yes, I am running what is basically a 2.0R system :-| )

Gary