Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!husc6!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Re^2: Functions pointers and stuff.
Message-ID: <9952@smoke.BRL.MIL>
Date: 30 Mar 89 16:23:16 GMT
References: <1715@leah.Albany.Edu> <3182@goofy.megatest.UUCP> <301@oha.UUCP> <1989Mar29.204918.3882@utzoo.uucp> <302@oha.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <302@oha.UUCP> tony@oha.UUCP (Tony Olekshy) writes:
> b) Deliberately make the name of the binary known during the installation
>    process, and check the consistency of this information at run-time.
>    This is an alternative which meets the needs set out in the original
>    posting.

It's unworkable, especially in a true networked environment, but even
in traditional UNIX environments where an executable binary need not
be readable to its invoker.  (So you still can't read the name list.)
Also, a stripped executable may not have a name list.