2 ms·
Who says it’s defeatist? It’s realism. You might as well say noting mild steel only has a 60-80kpsi yield strength ‘defeatist’. That attitude allows practical
by lazide 2y ago
Who says it’s defeatist? It’s realism. You might as well say noting mild steel only has a 60-80kpsi yield strength ‘defeatist’.
That attitude allows practical risk management and effective engineering. Pretending software can be secure or mild steel has infinite yield strength cannot.
There is no lock that can’t be picked either, which is why no one leaves millions in cash protected just by a lock without guards and a surveillance system. And why they insure large amounts of cash.
At this point it should be pretty obvious - don’t put important secrets on computers without a way to expire/revoke them. If it’s a secret that can’t be expired/revoked, think long and hard about if you need it on a computer - and if you do, use a SCIF.
Monitor any connected computer systems for compromise. Use encryption extensively, preferably with hardware protection, because software is insecure, etc.
Same with controlling dangerous equipment - don’t rely on pure software or someone will get killed. Use hardware interlocks. Use multiple systems with cross checking. Don’t connect it to the internet. Etc.
This is all industry best practice for decades now.
- wruza 2y agoBut the initial dialog was more like Q: this is good steel still, why not use it? A: steel is never ideal, that's the problem. Oh really. Risk manage us nginx please. At least write out the steps, you must have a checklist or something, right? Let's be honest, we just apt install it and read vulnerability reports when they hit /news.
- oopsallmagic 2y agoExactly. I don't believe that the argument that some software somewhere at some point could have some vague security flaw in it is usually good enough to justify not running the kinds of software most of us here work on. It's solipsistic, and honestly seems a little in bad faith. But it's also moot: if you're that afraid of vague security threats, then just don't expose your software to the internet. It's not difficult.
- lazide 2y agoLiterally never said that. Speaking of bad faith. the whole point in context was that exposing software to the internet is high risk, no matter how secure you think it is, because no software is truly ever secure given enough exposure. Talk about exhausting bullshit. But then what to expect from a green throw away?
- oopsallmagic 2y ago> Who said it's defeatist? Uh, me, I did. I thought I was pretty clear. Please refer to my previous comment. > It's realism. Okay. How are you going to change your behavior? I'm not sure what point you're trying to make. If you want to put your recipe website behind a SCIF, be my guest. Some of us aren't quite so afraid.
- lazide 2y agoHaha, pot calling kettle black. I don’t need to do a damn thing different. Cars are still dangerous 100 years after they were invented, and the world still turns. You’re the one trying to turn this into some kind of existential emergency. What are you going to do differently?
- oopsallmagic 2y agoNothing! That's my entire point! Because I'm not afraid of the internet, and I trust in my ability to secure the software I host. You're the one struggling with the fact that no software is a platonic ideal, while the rest of us still have jobs to do.
- lazide 2y agoThen you may want to look into defense in depth - or at least not store any valuable secrets on the same machine, or accessible to that machine. Which is my point. Or yolo it because you don’t care about a compromise. It’s your life, not mine. Hopefully you aren’t storing any medical records, financial records, etc. for me or anyone I care about if that is the case though.