From owner-freebsd-questions Tue Jul 22 02:03:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17721 for questions-outgoing; Tue, 22 Jul 1997 02:03:16 -0700 (PDT) Received: from ns.cs.msu.su (laskavy@redsun.cs.msu.su [158.250.10.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17715 for ; Tue, 22 Jul 1997 02:03:09 -0700 (PDT) Received: (from laskavy@localhost) by ns.cs.msu.su (8.8.6/8.6.12) id NAA13668; Tue, 22 Jul 1997 13:01:06 +0400 (DST) Date: Tue, 22 Jul 1997 13:01:06 +0400 (DST) Message-Id: <199707220901.NAA13668@ns.cs.msu.su> From: "Sergei S. Laskavy" To: tims@dcs.state.ar.us CC: freebsd-questions@FreeBSD.ORG In-reply-to: (message from Tim Stoddard on Mon, 21 Jul 1997 13:57:56 -0500 (CDT)) Subject: Re: suid question Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "Tim" == Tim Stoddard writes: Tim> I have a need to allow someone the ability to reload a Tim> daemon. I have tried to write a script with the suid id bit Tim> set and owner set to root, but the script is always executed Tim> with the uid of the person who executed it instead of root. Tim> I am at a loss as to what else would need to be set. I guess, "sudo" can help you. This is advanced "su" program. It is avaliable from "packages" or "ports" collections. Shell is very insecure and can not be used for writing setuid scripts. Sergei S. Laskavy