Editing 1200: Authorization
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
β | + | Computer {{w|Operating system|operating systems}} were initially written for the business environment. Thus they were made to be accessible to multiple employees, or {{w|User (computing)|users}}, but only fully accessible to {{w|System administrator|administrators}} (or admins). Regular users can access and use {{w|Application software|programs}} on the computer, but only the admin is allowed to make changes to how the computer runs. This same split level of security continues to this day, even in privately owned, or "home", computers. | |
β | The | + | The joke here is that the most important things on a computer are no longer the programs that it runs, but the private personal data it accesses (usually online). Anyone who wished to do real mischief on an active computer could do {{w|Identity theft|considerable damage}} without ever caring what the admin password was. The admin password, in effect, now guards a vault no one cares about. |
This comic pokes fun at the {{w|authorization}} mechanisms surrounding most operating systems' administrator accounts. It makes the argument that the user's data is more valuable than the integrity of the system. This is arguably true for most personal systems, although it is probably not true in a shared-server setup, where a system compromise could lead to the exposure of many users' data. | This comic pokes fun at the {{w|authorization}} mechanisms surrounding most operating systems' administrator accounts. It makes the argument that the user's data is more valuable than the integrity of the system. This is arguably true for most personal systems, although it is probably not true in a shared-server setup, where a system compromise could lead to the exposure of many users' data. |