Xref: utzoo comp.bugs.4bsd:887 comp.bugs.misc:175 comp.bugs.sys5:507
Path: utzoo!utgpu!water!watmath!clyde!mcdchg!ddsw1!tarkus!jcs
From: jcs@tarkus.UUCP (John C. Sucilla)
Newsgroups: comp.bugs.4bsd,comp.bugs.misc,comp.bugs.sys5
Subject: Re: Hard Links between UNIX Utility Programs
Summary: Try --x
Keywords: unix links bsd sysv sys5
Message-ID: <218@tarkus.UUCP>
Date: 30 Jul 88 01:41:54 GMT
References: <184@chip.UUCP> <185@chip.UUCP>
Reply-To: jcs@tarkus.UUCP (John C. Sucilla)
Organization: tarkus -- Calumet City, IL.
Lines: 18

In article <185@chip.UUCP> mparker@chip.UUCP (M. D. Parker) writes:
>First try.  Make another copy of /usr/ucb/sendmail and call it /usr/ucb/mailq.
>Programs no longer have HARD LINKs and can be protected individually.
>Complication here, if a user creates a SYMBOLIC LINK to the program as:
>	ln -s /usr/lib/sendmail mailq

How about changing the mode to rwx--x--x (711) so they can't copy it
or create new links but can still execute it?  Or do these "symbolic links"
let you get around permissions?  I don't know, I know 0 about symbolic links
but I've got a sneaking suspicion it's part of BSD UNIX.




-- 
John "C". Sucilla,  A silicon based life form.
       {att,chinet,ddsw1}!tarkus!jcs
  You have a better idea? Now's the time..