Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!ames!mailrus!ncar!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: RDUMP - socket permission problem
Keywords: dump bsd network
Message-ID: <14202@mimsy.UUCP>
Date: 28 Oct 88 08:21:49 GMT
Article-I.D.: mimsy.14202
References: <211@chip.UUCP> <7694@bloom-beacon.MIT.EDU>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 17

In article <7694@bloom-beacon.MIT.EDU> wolfgang@mgm.mit.edu
(Wolfgang Rupprecht) writes:
>PS. Serious hint: 
>-rwsr-sr-x  1 root     staff       50176 Jan  2  1988 /etc/rdump

[I removed the inode number.]  Actually, this is much better:

-rwsr-s---  1 root     operator    51200 Nov 18  1987 /etc/rdump

along with

-rwxr-s---  1 bin      operator    36864 Nov 18  1987 /etc/dump

Others are possible, but be careful not to let anyone read the raw
disk devices, lest your file protections not protect.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris