Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!hsdndev!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.wizards
Subject: Re: Wizard-level questions
Message-ID: <13616:Feb621:46:0191@kramden.acf.nyu.edu>
Date: 6 Feb 91 21:46:01 GMT
References: <16048@sdcc6.ucsd.edu> <395@appserv.Eng.Sun.COM> <19029@rpp386.cactus.org>
Organization: IR
Lines: 25

In article <19029@rpp386.cactus.org> jfh@rpp386.cactus.org (John F Haugh II) writes:
> In article <395@appserv.Eng.Sun.COM> lm@slovax.Eng.Sun.COM (Larry McVoy) writes:
> >In article <16048@sdcc6.ucsd.edu> cs163wcr@sdcc10.ucsd.edu (I support the U.N.) writes:
> >>[1] Can you access a file by its i-node number?  Something like
> >>	(for C code) FILE *iopen (int inode, char *mode) ?
> >Program included below.  This program does an internal file tree walk
> >to find the inode.  Slow, but quite portable, contrary to a supposed
> >wizard's opinion.

I'm still wondering who you were trying to insult, Larry... Can we ask
that you make sure your code satisfies the spec given before posting it?

> Dan incorrectly
> stated that it was a security whole if it could be executed
> by mortal users - no, it is only a security whole if it is made
> to work for mortal users.

I stand corrected. Thanks.

> Furthermore, it does not appear to address mount
> points at all.

Oops, another problem I missed. Good point.

---Dan