4 ms·
When is the last time leaving your keys in the car caused your house to suddenly slide 10 foot southwest? When is the last time you flipped a light switch, and
by mikewarot 6y ago
When is the last time leaving your keys in the car caused your house to suddenly slide 10 foot southwest?
When is the last time you flipped a light switch, and suddenly your pool disappeared?
Have you ever had French doors appear in your dining room because of a "Windows Update" on Wednesday morning?
Have you ever had to wait for half an hour for your house to boot later on that same Wednesday?
When is the last time you closed a door, and were killed by a hailstorm of bowling balls?
At least with a light switch, you know it's very unlikely to cause structural issues, or plumbing issues, or drain your bank account. Computers are singularly horrible in the ways things can fail.
- scubbo 6y agoI agree with your underlying point, but it's also important to point out that computers are also singularly wonderful in that it's usually much faster and easier to reverse failures, and then to diagnose and debug in a non-impactful manner. To take your second example - if I could then flip the light switch back, and the pool reappeared, then I'd be miffed but not particularly annoyed (assuming I was able to fix that obvious-bug either myself or with an update in a timely fashion). If the pool stayed gone, then yeah, I'd be pissed. Of course, that whole argument goes out the window when the tech in question isn't controlled by you. Which is often the case.
- salawat 6y agoTell that to the 346 people who perished because of negligent and (in my opinion, malicious in terms of regulatory deception) undocumented, uncommunicated programming of the speed trim system of the 737 MAX. Or the folks who perished because of badly programmed software interlocks on the THERAC-25 radiotherapy machine. Just knowing or figuring out to flip that switch may be an insurmountable barrier depending on the circumstances when a failure state occurs. Especially when the implementation is intentionally hidden so as to facilitate continued market value extraction opportunities from the happy accident of information asymmetry.
- antipaul 6y agoI agree with the sentiment of the post and the replies. Yet your examples hint at something more. Those massive failures are by people not by tech. Mismanagement and incompetence and systems designed to obfuscate accountability. Which happens aplenty in non tech fields.
- mikewarot 6y agoIn wiring a house, there is a built in assumption that something could go wrong and disrupt the wiring. That's why we had fuses, and now circuit breakers, grounding, ground fault interrupters, metal conduit, etc. All of these serve to limit the side effects of faults. When you turn on a switch... it's part of a circuit which is current limited, and in fact there are several limits on that current, all the way back to the source... each designed to protect a link in the chain. Each of those breakers limits the capability to source current further downstream. When you run a task in any modern OS, it runs with the full privileges of the user id with which it was launched. This is like hooking a generating station directly up to your floor lamp in the living room with no breakers. If the process has a fault, there is nothing the Operating System will do to prevent it from being used to subvert other parts of the system, there is no limit to what it can do. There are systems that require you to specify how many resources a given task is to be allowed to access. It turns out that such systems can be just as user friendly as the ones we're used to, but they do require things be re-written because the ground assumptions in the security model are different. Capability Based Security (also known as "Multi-Level Security) was born out of a need to have both Sensitive and Secret information shared on a computer that scheduled Air Traffic during the Vietnam Conflict. (If I remember the situation correctly) The flights themselves were sensitive, and the locations of the enemy radar were top secret (because people risked their lives spying to find them). It was extremely important that information could not leak, and solutions were found, and work! About 10 years ago, when I learned about this, and considered the scope of work required to make it available in general purpose Operating Systems, I estimated it would take 15 years until the need for Capability Based Security would be realized, and another 5 more or so until it was ready. I think we're on track.... 2025 people will start adopting it, and 2030 it will be the defacto way things are done. Genode is a long standing project to bring this new type of security to the masses... I'm still waiting until the point I get to play with it... and have been for a while. Things will get better... these types of tools, along with "information hiding", getting rid of raw pointers and other clever but dangerous tricks will help as well. [Edit: Re-arranged to clarify, and improve flow]
- hrktb 6y agoI’d argue computer programs failing mode are often less gruesome that real life’s gas and electric failures. As a kid we had a gas range, and it was pretty easy turn on a burner and just leave it open without lighting it. Or just start cooking something and forget about it, depending on your situation your house is gone.
- Aeolun 6y agoNormally the gas has quite a distinctive odor just for these kinds of situations. Sucks if you leave your house and enter it again lighting a cigarette though.
- monksy 6y agoWhens the last time that you had a car door working door, and it fell off when you opened it? (MVP, no tests) [I'm not talking about a worn out car]
- titzer 6y ago> When is the last time you flipped a light switch, and suddenly your pool disappeared? Or the pool just disappeared for no reason and you couldn't get it back unless you sold your house and rebought it?
- Aeolun 6y agoI don’t know where you got these examples, but they were fantastic.
- mikewarot 6y agoJust trying to make analogies people can understand over the years. The current state of computer security.... is like building a fort, out of cases of C-4 explosive. How so? Almost every program has bugs, many of which can be exploited remotely. It is effectively impossible NOT to have a zero-day exploitable hole in any given computer. Thus, every single computer can be exploited... and then used to attack more computers.... in a chain reaction.... like a fort built out of C-4.