On Apr 3, 2014 5:59 PM, "Duncan" <[email protected]> wrote:
>
> Kfir Lavi posted on Wed, 02 Apr 2014 13:38:47 +0300 as excerpted:
>
> > What I don't understand is, why it needs to get write permissions to
> > /etc/mtab ?
>
> That is a worrisome indeed, since /etc/mtab is now often a symlink to
> /proc/self/mounts (or to /proc/mounts which in symlinks to /proc/self/
> mounts), which is kernel-enforced read-only.
>
> Either way, attempts to write to the symlink target (/proc/self/mounts)
> *OR* to replace the symlink are worrisome, tho attempts to write the
> target only potentially disrupt the writer, while successfully replacing
> the symlink could leave a system and thus its sysadmin in a world of hurt.
>
> Yet another lesson on the evils of proprietary/servantware code and the
> violation of the freedom of actual users to properly see what's going on
> and to fix it. <shrug>
>
> --
> Duncan - List replies preferred. No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master." Richard Stallman
>
>
I think the developer of install shield just open it for reading with a
read write call.
I'm with you on every word you wrote.
