Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mgm.mit.edu!wolfgang
From: wolfgang@mgm.mit.edu (Wolfgang Rupprecht)
Newsgroups: comp.unix.wizards
Subject: Re: RDUMP - socket permission problem
Keywords: dump bsd network
Message-ID: <7694@bloom-beacon.MIT.EDU>
Date: 28 Oct 88 00:58:38 GMT
References: <211@chip.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: wolfgang@mgm.mit.edu.UUCP (Wolfgang Rupprecht)
Organization: Freelance Software Consultant, Boston, Ma.
Lines: 18

In article <211@chip.UUCP> mparker@chip.UUCP (M. D. Parker) writes: 
>In my zeal to properly protect files in my UNIX system, I seem to
>have caused /etc/rdump to stop working.  A similar problem happens
>when I do /etc/ping to another site.  A note here is that /etc/ping
>will work correctly when executed as ROOT.  Question, what did I
>break and how do I fix it?

How about a set-UID shell script to let users run these programs? ;-)

-wolfgang

PS. Serious hint: 
  22 -rwsr-xr-x  1 root     staff       22528 Jan  2  1988 /etc/ping
  49 -rwsr-sr-x  1 root     staff       50176 Jan  2  1988 /etc/rdump
---

Wolfgang Rupprecht	ARPA:  wolfgang@mgm.mit.edu (IP 18.82.0.114)
TEL: (617) 267-4365	UUCP:  mit-eddie!mgm.mit.edu!wolfgang