prelink should not mess with running executables
Tomasz Torcz
tomek at pipebreaker.pl
Tue Jul 17 11:05:50 UTC 2012
On Tue, Jul 17, 2012 at 07:01:23AM -0400, Sam Varshavchik wrote:
> Andrew Haley writes:
>
> >On 07/17/2012 12:38 AM, Sam Varshavchik wrote:
> >> Jan Kratochvil writes:
> >>
> >>> On Sun, 15 Jul 2012 22:42:00 +0200, Sam Varshavchik wrote:
> >>>> And I wouldn't be so presumptions as to state authoritatively what
> >>>> is or is not a bug, in something whose purpose is not known to me.
> >>>
> >>> Non-existing /proc/self/exe file is a normal UNIX process state so a UNIX
> >>
> >> It is anything but "normal". The "normal" state of things is documented by
> >> proc(5). As documented by that man page, rather plainly,
> >> readlink("/proc/self/exe") gives you your own pathname.
> >
> >Yes, it's the pathname that started this process. Yes, that pathname
> >may point to file that no longer exists. That's UNIX.
>
> No, that's Linux with prelink installed.
But pathname is volatile. That's why we support security framework based
on labels, not on pathnames...
--
Tomasz Torcz Only gods can safely risk perfection,
xmpp: zdzichubg at chrome.pl it's a dangerous thing for a man. -- Alia
More information about the devel
mailing list