>>
> I'm surprised to hear this - it seems to go against the philosophy that
> someone with root permission should know what they are doing, and is working
> without protection on purpose.
That's not exact:
Root account should NEVER been used in production environments. You
should use sudo instead.
Apart of that, a welder also should know what he are doing while
managing soldering iron. But leaving things disordered in its
workspace is always a bad idea. Even when you know exactly what you
are doing.
Similarly, having execution permission for file, like plain text or
html, which is not designed to be executied, is a bad idea:
First because you probably took less care about write access to that
file because you didn't planed to execute it.
And, second because, anytime you can, for example, forgive to type
'vim' before the file name when trying to edit it.
...And I didn't talk about suid permission (which lets any user with
execution permission to execute the file as if he were the owner
--temporary "becoming him"--) ...but this permission is never set in
usual umasks like when mounting not permission-enabled filesystems.
Regards.
--
Joan Miquel Torres__________________________________
Linux Registered User #164872
http://www.mallorcaweb.net/joanmiquel
BULMA: http://bulma.net http://breu.bulma.net/?l2301
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment