Xref: utzoo comp.bugs.4bsd:903 comp.bugs.misc:180 comp.bugs.sys5:519 Path: utzoo!attcan!uunet!mcvax!hp4nl!philapd!ssp10!willy From: willy@philapd.UUCP (Willy Konijnenberg) Newsgroups: comp.bugs.4bsd,comp.bugs.misc,comp.bugs.sys5 Subject: Re: Hard Links between UNIX Utility Programs Keywords: unix links bsd sysv sys5 Message-ID: <106@ssp10.idca.tds.philips.nl> Date: 6 Aug 88 20:59:37 GMT References: <184@chip.UUCP> <185@chip.UUCP> <218@tarkus.UUCP> <153@ispi.UUCP> Organization: Philips TDS, P.O. Box 245, 7300 AE Apeldoorn, The Netherlands Lines: 22 In article <153@ispi.UUCP> jbayer@ispi.UUCP (id for use with uunet/usenet) writes: > >Another workable solution is to do the following steps: > 4. Make the owner of the shell script the super user > 5. Set the user bit for the shell script (chmod u+s name) This works only if you have a shell that acknowledges the suid bit! The Korn shell does that ONLY IF explicitly installed to do so, the standard SV Bourne shell does NOT. I don't know about the C-shell or any other shells. If your shell does not handle the suid bit, you will have to write a small front end in C to call the shell script. This front end merely does an execvp of the shell script with it's argv. BTW, You could have the shell script check it's arg0 to determine the action to be taken, and use links to make all "sensitive" commands end up in this single shell script. (Weren't links the original problem? :-) -- Willy Konijnenberg Philips Telecommunication & Data Systems, Department SSP/V2. Apeldoorn, The Netherlands.