Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site ncoast.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!zehntel!dual!amd!decwrl!decvax!cwruecmp!atvax!ncoast!bsafw From: bsafw@ncoast.UUCP (The WITNESS) Newsgroups: net.unix-wizards Subject: Re: Is the restricted shell really secure? Message-ID: <213@ncoast.UUCP> Date: Tue, 31-Jul-84 09:46:24 EDT Article-I.D.: ncoast.213 Posted: Tue Jul 31 09:46:24 1984 Date-Received: Sat, 4-Aug-84 01:32:22 EDT References: <275@pcsbst.UUCP> <990@inuxc.UUCP> <280@genrad.UUCP> <210@ncoast.UUCP> <212@ncoast.UUCP> Organization: North Coast XENIX, Cleveland Lines: 15 The problem is that "smart" file system checkers (i.e. "fsck") will also check to make sure that "." points to the current directory and that ".." points to its parent. Running fsck on a filesystem with ".." pointed to "." will cause everything from that point on to be discarded by fsck. (It is much more likely that something damaged the filesystem than that someone unlinked ".." -- so the designers of fsck would have thought.) What I'm after is a means of protecting the filesystem without unlinking or modifying the directory links. Can anyone help -- Brandon Allbery: decvax!cwruecmp{!atvax}!bsafw 6504 Chestnut Road, Independence, OH 44131 Witness, n. To watch and learn, joyously.