5 ms·
> No company in the industry has spent more to address security than Microsoft Then they sure did a shitty job. One thing that comes to my mind ... those obno
by bad_user 17y ago
> No company in the industry has spent more to address security than Microsoft
Then they sure did a shitty job.
One thing that comes to my mind ... those obnoxious UAC screens. I've never had problems on Linux or Mac to type my password for escalated privileges ... but UAC I had to turn off because it was too annoying.
Also, until Win XP SP2 no firewall wasn't included in the Windows distribution. Not to mention all kinds of services that are active by default without the user needing any of them.
I'd sure like to know where those money went.
- tptacek 17y agoHere, let me help you with that: how about, by spending tens to hundreds of thousands of dollars per release to have 80% of the software security assessment industry test their products on the dot release? How about, by delaying the release of major revisions of their code, on multiple occasions by multiple months, to re-audit for vulnerabilities when a single instance of them is found during last-minute testing? How about, by forcing every single developer in the company to be trained in writing secure C code? (Book jacket of very popular secure coding book: "Required reading at Microsoft - Bill Gates". Hacker News comment from former MSFT developer a couple days ago: "That book actually was required reading at Microsoft.") Or by deprecating the worst of the old C string interfaces, then banning them across their code, and then auditing against that? I can see where the disconnect is between you and me on this issue. I've actually worked with them on some of this stuff. Far less than many other people in my field. But the UAC and firewall stuff isn't even on my radar.
- prodigal_erik 17y ago> trained in writing secure C code The hubris here is astonishing. After this many decades, hasn't the entire industry adequately demonstrated that that almost all programs have mistakes and that most mistakes in C become security flaws? I've contracted there, I've sprinkled some proprietary buffer annotations around their legacy code, and I'm still not convinced that's enough to make unchecked pointers a reasonable way to write apps.
- tptacek 17y agoWe might just as productively argue about politics or religion, but I'll sum my response up by saying that roughly 60% of the apps we assess (assessing app security being my day job, and what the company I cofounded does) have no C in them, and those apps are not "more secure" than the apps with C code. Should "you" write C code? No. You don't have to. You will screw it up in amusing and horrible ways. But don't suggest Microsoft should rewrite Office in Haskell. All that would happen if they did is that we'd learn how to exploit insecure Haskell idioms real fast.
- prodigal_erik 17y agoI get that I could write my security model incorrectly in any language. My objection to C is that unchecked pointers can be used to arbitrarily corrupt parts of the program that would otherwise work correctly. But it sounds like you've found that removing these infamous classes of vulnerabilities doesn't actually help--can you explain why that is?
- tptacek 17y agoBecause there are many other infamous classes of vulnerabilities, many of which are abetted by high-level languages. You don't find a lot of "remote file inclusion"-style flaws in C code, for instance.