Most network file systems still appear to be local accesses so this IS
still a valid idea. I think it is unreasonable to expect users to be
able to make reasonable judgements about how a particular command might
effect there system. Do YOU really think that there is no one clever
enough to fool YOU with some cryptic UNIX trojan link. The average
user isn't competant enough to tell whether some command will destroy
his system, therefore tight control should be exercised with this
link type. Another issue is how can a single executable link be useful
on other systems? Why should a machine specific link be usable across
the network? We are playing with fire with this link type, I know this
from experience.
My suggestion would be to allow "exec:" type links to be run only if
the file that contains them resides on the local filesystem. (physical,
NFS, AFS, etc.) Or a file that resides on a trusted host. (in a list?)
That way there is at least some sense of security.
:lou
-- ************************************************************************** * T H E U N I V E R S I T Y O F K A N S A S * * Lou MONTULLI @ Ukanaix.cc.ukans.edu * * Kuhub.cc.ukans.edu ACS Computing Services * * 913/864-0436 Ukanvax.bitnet Lawrence, KS 66044 * * UNIX! Cool! I know that! Jurassic Park - The Movie * **************************************************************************