4 ms·
> But the constant asking for permission dialogs, while a security improvement It wasn't a security improvement. For one, it mostly just got in the way and tr
by AnIdiotOnTheNet 9y ago
> But the constant asking for permission dialogs, while a security improvement
It wasn't a security improvement. For one, it mostly just got in the way and trained users to ignore it, negating the purpose of its existence, but it also never protected the user from anything. Case in point: ransomware needs no elevated permissions.
- user5994461 9y agoIt trained developers to develop their apps properly to not need a prompt.
- rossy 9y ago> Case in point: ransomware needs no elevated permissions. That's the result of how we drew up the security boundaries on desktop operating systems. You don't need admin permissions to rewrite your most important documents, so ransomware running under your user account doesn't either. See also: https://xkcd.com/1200/ https://xkcd.com/1200/ Linux and macOS have this problem too. The solution isn't to remove the security boundary between the user and admin accounts and to go back to the Windows 9x-era of having zero OS-level security. The solution is to create more security boundaries, so that not every program running on your behalf has the permission to rewrite all your documents. UAC was an unpopular, but not totally ineffective step in the right direction.
- AnIdiotOnTheNet 9y agoI disagree, because it's the user's system and they should have permission to change anything they want in the system, that security boundary serves only to annoy the user for no gain whatsoever. What our real goal is, is to prevent misbehaving applications from compromising the user's work. Obvious conclusion: permissions boundaries should be on the applications. On this we agree.