In message <[EMAIL PROTECTED]>
Brian Fundakowski Feldman writes:
: It sounds to me that what you really want are the semantics of a
: symbolic link and not the semantics of a hard link. Is it just me,
: or does it seem as if the pathname of the executable being stored as
: a virtual symlink in procfs as "file" would solve these security
: problems?
If you can get to the full path to the original file, this is likely
the answer. I don't know if that information is easily available or
not. My memory of the proc structure is that it has a vnode to the
executable, which is easy to produce as an alias in /proc/xxx/file,
but much harder to get the original path to.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
