Date: Sat, 06 Nov 1999 23:51:05 -0700 From: Warner Losh <imp@village.org> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: freebsd-hackers@FreeBSD.org Subject: Re: Procfs' pointers to files. Message-ID: <199911070651.XAA03143@harmony.village.org> In-Reply-To: Your message of "Sat, 06 Nov 1999 15:54:50 EST." <Pine.BSF.4.10.9911061552120.846-100000@green.myip.org> References: <Pine.BSF.4.10.9911061552120.846-100000@green.myip.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.10.9911061552120.846-100000@green.myip.org> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911070651.XAA03143>