The MS-DOS Security Model
theinvisiblethings.blogspot.com
theinvisiblethings.blogspot.com
This is a great example of tech people falsely generalizing their experience and habits to those of non-tech people. There are many, many families with one computer that the entire family shares.
http://tvtropes.org/pmwiki/pmwiki.php/TroperTales/PornStash
My favorite is the guy who uses the Purloined Letter method: he just keeps it on the desktop in a folder named "New Folder". Though some people's obfuscated unicode path name tricks are pretty nice, too.
The article should have been called the "Minicomputer security model" BTW, because that is what we are mostly stuck with.
man sandbox
Since 10.5. Many applications don't use it, however. But if you're going to be running remote code (ie, your application has a plugin architecture), you can use this to make things as secure as you desire. And, if I remember right, Apple's own software is sandboxed (ie, Pages, etc).Frankly, I was expecting this to be a pro-DAC (SELinux/grsecurity/TrustedBSD) article.
This problem is largely getting solved, by web applications. Make little applications in the form of websites, and people can use it safely as long as the web browser does not have a security hole.
Running different applications as different users on a desktop machine is too much trouble anyway.
In practice this means: "Make little applications in the form of websites, and people cannot use it safely."
I would like to be able to downvote this stupid rant :)
It's not reasonable to expect non-technical people to create a user account for each app they want to download and use from the Internet.
I'm sure there are some very nice web apps for that out there. I don't install programs I don't intend to run at least weekly anymore, with very few obvious exceptions.