~/.macports
René J.V. Bertin
rjvbertin at gmail.com
Thu Feb 12 04:13:38 PST 2015
On Thursday February 12 2015 12:33:53 Clemens Lang wrote:
> You should be aware of the security implications of this change. For example,
> sudo port edit vim gets you arbitrary code execution and arbitrary file access as
> root.
Exactly one of the reasons I don't like rendering sudo implicit, and even less strip it of its pw protection.
I really prefer to take my chances making select parts of the FS writable to the admin group, and allow non-privileged port to write to my home directory. There's nothing in there that I cannot restore from backup. The same applies for the rest of the system, but recuperating from a borked OS or from a borked $HOME are not exactly comparable in terms of effort.
R.
More information about the macports-dev
mailing list