11 ms·
> There are too many changes. I am sorry, security guys, but unless it's military-grade software, security is just another feature. And it is not a highest pri
by atemerev 10y ago
> There are too many changes.
I am sorry, security guys, but unless it's military-grade software, security is just another feature. And it is not a highest priority one. Of course, security would be easier if there were no new features or spec changes. And software development in general would be much easier if there weren't any of those pesky end users.
Which is a good thing, probably. Otherwise, you'd be mostly out of your jobs. Security is always changing, chaotic battlefront.
Having said that, sandboxing is a good idea. Theoretically. But it is really hard to implement right — attack surface on the edges of the boxes is quite large. Remember those Java applets? They were sandboxed neck-deep, with excellent security model. Did it help?
- wtbob 10y ago> I am sorry, security guys, but unless it's military-grade software, security is just another feature. And it is not a highest priority one. I completely disagree: security is the foundation of any software system. Without security, the system simply cannot be trusted to do anything correctly, not even add 1 and 1 together. For far too long we've relied on our systems being accidentally correct rather than deliberately secure; we need to fix that. If something's mathematically possible, then it will happen. We need to build systems where security flaws are impossible, because then … they won't happen.
- verbify 10y agoJust for the record: > So I personally consider security bugs to be just "normal bugs". I don't cover them up, but I also don't have any reason what-so-ever to think it's a good idea to track them and announce them as something special. Linus Torvalds - http://yarchive.net/comp/linux/security_bugs.html http://yarchive.net/comp/linux/security_bugs.html Here's a lengthier article about it - http://www.washingtonpost.com/sf/business/2015/11/05/net-of-insecurity-the-kernel-of-the-argument/ http://www.washingtonpost.com/sf/business/2015/11/05/net-of-...
- JoBrad 10y agoI'm not sure it's mathematically possible to reduce your attack surface to 0.
- Ygg2 10y agoSure it is. Just take your computer, put it in a furnace, turn it to ash and bury it couple of feet in the ground. Now its attack surface is 0.
- allendoerfer 10y agoYou would first have to verify the furnace and the "turn it to ash" process.
- bluejekyll 10y agoAnd the ash itself has to be perfectly random, otherwise someone could reverse the burn and reconstruct the computer.
- nimmer 10y agoSee "perfect solution fallacy"
- hyperpape 10y agoIt's not a fallacy if you're responding to someone who says "we absolutely must have a perfect solution"
- wtbob 10y agoFWIW, I'm not saying we must have a perfect solution: I'm saying that we have to build systems which make the implicit failings of their imperfect solutions explicit. As an example, it is impossible to build a system which gives one person access without permitting that person to lend that access to others: we need to acknowledge that rather than pretend it's untrue.
- cesarb 10y ago> Without security, the system simply cannot be trusted to do anything correctly, not even add 1 and 1 together. Not really. For a simple example, imagine a calculator software which has been mathematically proven to work correctly for any number with 30 or less digits, but which overflows a fixed-size buffer if the user inputs a number with more than 30 digits. That software could absolutely be trusted to add 1 and 1 together, while still having a security issue.
- btrask 10y agoThe idea is to separate security out so that new features and spec changes don't impact it. The necessary features of the sandbox are defined by the hardware, which doesn't change very fast. Everything else can be done inside the sandbox, without worrying about security. Java applets are another example of security competing with features. Any part of the runtime could cause an exploit. If the sandbox had been separate it would've been safer.
- 3pt14159 10y agoThe thing that you're missing here is that some of us do work on military-grade software and we still need to use a browser. We need to trust that going to a website won't leak information off of our HDs. I know a guy that builds fighter aircraft displays out of a giant clean room he built in his home. He was writing code for it on the same computer he was using for day to day work because he didn't really know any better (more of an Electrical Engineer than a software dev). My point is that you don't get to use the "it's just another feature" with some of this stuff. For Counter Strike, sure. But for things like spreadsheets or web browsers, hundreds of thousands or millions of people working in arms manufacture or intelligence are going to be using your software and it needs to not leak designs to foreign intelligence agencies or competitors.
- ZenoArrow 10y ago> "The thing that you're missing here is that some of us do work on military-grade software and we still need to use a browser." Then use Qubes OS: https://www.qubes-os.org/ https://www.qubes-os.org/ You can set up a separate VM in Qubes OS purely for browsing. That way, even if your browser was compromised, it would be isolated from your other applications.
- jahnu 10y agoThey need to fund development of a military grade browser then. Perhaps that might be a better investment than the F-35 for example?
- youdontknowtho 10y agoThat was awesome.
- syngrog66 10y agoI bet it would burn through a billion dollars, require a team of hundreds, take 10 years, then be so buggy would get cancelled. I started off talking about the browser, not the F-35, but by the end the line blurred. :-)
- kelvin0 10y ago