![]() ![]() This may actually end up with the user delaying updates or admin maintenance, just to save time and postpone dealing with the hassle. On the other hand, it is a pain to switch to your admin account, then switch back to your standard account, back and forth.Basic lines of defense (firewall, running trusted apps, and so on) are system wide.If a bad app wants to send home your docs, it can perfectly do so from a standard account. As far as I know, even when used from a standard account, apps have full access to the user’s personal files and have full network access (minus any firewall, etc.). For spyware, privacy concerns and this kind of stuff, using standard accounts provides little additional protection, if any.What’s more, in sensitive places where they are still allowed, such modifications would require a root password at the very least, even from an admin account, bringing us back to the first argument. Deep OS modification or code injection into most critical files has been prevented by SIP from El Capitan, whether your are admin, root or nobody.Any app wanting to go root will ask for your password anyway, so I see no additional security layer here. OS X admin accounts are not root accounts.This seems to be common advice in the Windows world, but for an up-to-date OS X system, I just cannot understand what kind of benefits it brings. It should be a standard account created for this purpose, and you should log to the admin account only to perform actual admin tasks. » ![]() "Your ‘everyday’ user account should not be an admin account. I have seen it a lot recently, on a number of Mac websites or forums. This piece of advice is old but is coming back into fashion.
0 Comments
Leave a Reply. |