4 ms·
Microsoft answered Congress' questions on security. The White House needs to act
- jmholla 2y agoThat testimony was so empty, and the fawning over Smith's "acceptance of responsibility" felt silly given they've demonstrated no real plan for correcting their course and rectifying their past mistakes. In addition to the things pointed out in the article, some highlights from watching it myself: * Smith mentioned that individual contributors (ICs) will have security as a part of their individual assessments affecting their take home pay, but further digging revealed that this could be as little as 3% of their salary, and much less when factoring in stock. And, project managers are not subject to this. His response to that was people love to get straight A's in Silicon Valley. This feels like a way for them to place future blame on ICs. * At one point concern was raised about ransomware's impact on rural hospitals. Smith said they were working with hospitals to give them discounts of 75% or even free, for the first year. I would've liked to see them talk about why security is a paid for add-on instead of necessary part of the base product. * On that ransomware point, Smith said the best solution was to pressure Moscow to stop their people from deploying ransomware, while rambling on about our alliance with the Soviet Union in World War 2. What a silly, ineffective approach and silly tangent to go on. * He talked about how finding these security issue was everyone's job and how happy he was that the State Department had brought one such issue to their attention. I was happy to see when one of the representatives pointed out that the government pays them to do that job, specifically. * He seem woefully under-prepared to talk specifics about some questions, but to me it just felt like there weren't good answers and feigning lack of knowledge was a way to sidestep the line of questioning. * When it came to Recall, he liked to talk about how it wasn't a "released" product and praised themselves on the changes they'd made to their approaches, conveniently leaving out that many of the flaws in their approach were pointed out after their "non-releases" to the public. All in all, Brad Smith's answers were mostly empty, often pandering, and deceptively self-aggrandizing (self being Microsoft). Admittedly, I didn't have a high opinion of Microsoft before this hearing, but this definitely made me think even less of them. The government needs to take a long hard look at their vendors' and their own approaches to software security.
- tonetegeatinst 2y agoYeah even windows 10 was seen as a privacy nightmare, but iv always know Microsoft just blows when it comes to security. They just don't patch shit sometimes, I can't trust they arnt backdoored. They charge users for the product while mining user data. I knew it would be BS corporate speech, like it always is from them and certain companies. Its just sad to see this happen
- blackeyeblitzar 2y agoThanks for the detailed summary. I agree with your characterization of it being a mix of empty pandering and deceptive self-aggrandizement. But then again this is Microsoft. They have thrived on acting unethically just below the level of facing serious legal or regulatory consequences. Pointing fingers at ICs or the bizarre tangent about the USSR seems like a strategy engineered to gently deflect and distract while pretending to bear responsibility. But make no mistake - the weak legislators that won’t act against the cabal of giant tech companies are just as or even more guilty.
- hulitu 2y ago> But make no mistake - the weak legislators that won’t act against the cabal of giant tech companies are just as or even more guilty. They can't bite the hand that feeds them.
- pjmlp 2y agoYou see this difference between what is said and done in multiple places, where WinDev has influece, versus other business units like DevDiv and Azure. Hilo was a kind of response to the Longhorn development approach based on .NET, but using COM and C++ instead. Some surviving stuff, https://devblogs.microsoft.com/cppblog/announcing-hilo/ https://devblogs.microsoft.com/cppblog/announcing-hilo/ "So overall C++ is a good choice for writing Windows 7-based applications. It has the correct balance of the raw power and flexibility of C, and the sophisticated language features of C#. C++ as a compiled language produces executable code that is as close to the Windows API as is possible and, indeed, the C++ compiler optimizer will make the code as efficient as possible. The C++ compiler has many of options to allow the developer to choose the best optimization, and Microsoft’s C++ compiler is one the best ways to produce small, fast code. With such power and flexibility there are potential pitfalls, of course. The chief problem with C++ is the issue of memory management, but since it is a mature language, standard solutions have been developed, for example smart pointers. There are many established standard libraries and their longevity and maturity means that they are broadly used and tested and so can be trusted to be stable." Taken from https://learn.microsoft.com/en-us/previous-versions/msdn10/ff795785(v=msdn.10) https://learn.microsoft.com/en-us/previous-versions/msdn10/f... Followed by WinRT/UWP, being pretty much a revamped COM, with C++, and .NET bindings (although not for all WinRT scenarios). Which has pretty much stayed this way, and why .NET is more successful on Azure and cross-platform, than on Windows itself. So still looking forward when WinDev will take security more seriously.
- mensetmanusman 2y agoThe DoD should get serious about communication software.
- hilbert42 2y agoOnce things like this mattered (as in the days when components had to have second sources of supply). It seems to me (at least part) why consideration of these matters has slackened in recent decades is because there are many more things to process and to analyze them has become much more complicated. Even the most conscientious bureaucrat would be overloaded and unable to cope. Perhaps the only sensible way around this is to introduce high-level (broad) laws that require both corporations and their senior executives to act responsibly and to accept full responsibility for the quality of their products. As I suggested in my other post, if laws made it much easier for senior company executives to face criminal charges with regard to negligence, hiding faults from customers, etc. then they'd act more responsibly out of fear (these days they're too cocky that nothing will happen to them when things go awry and or their products go belly-up). A possible downside could be that fewer companies would tender for such contracts. That said, I reckon that situation would only be temporary until the message got through and sunk in. Also, such laws could easily be tailored to excuse those who made genuine mistakes, etc.
- hilbert42 2y ago"<...>report cited a now-ex-Microsoft whistle-blowing engineer who claimed he had repeatedly warned bosses as far back as 2017 about an authentication flaw<...> <...>the Kremlin spies used the SAML-based authentication flaw to gain full access to organizations' files and messages <...> via the backdoored SolarWinds software.<...> <...>was alleged Microsoft refused to fix this years-old problem because <...> [it would've cost MS billions whilst] vying for a massive IT contract with US fed gov<...>." I've long been a critic of Microsoft over multiple issues but I've been forced to the conclusion that expecting the corporation to make voluntary changes to its business practices is a waste of time simply on grounds that it doesn't make economic sense for it to do so. Years back in the halcyon days there was an expectation from both developers and computer users that new products both improved the state of the art and made profit for developers. That changed with Microsoft, like many, my early criticism of the company was that it was one of the first software companies that ruthlessly put profits before users' needs. As MS was a big influential software supplier with dominant, effectively monopolistic, control over products like MSDOS and Windows 95 its motives were blatantly obvious to us users. Why Microsoft's behavior was so obvious to many of us early computer users was that it contrasted strongly with our earlier experiences. Many of us had come from a hardware/electronics background and were experienced in using high quality state-of-the-art test equipment from renowned companies like Hewlett Packard† and Tektronix—companies that took great pride in the excellent products they produced. Their products were expensive but they were also damn good. Microsoft's products, were damned expensive, often short on user expectations, buggy and often bugs weren't fixed throughout the product's lifetime. With Microsoft what became very obvious to us was this manufacturer clearly had a different agenda, profits were more important than quality, and this was a very noticeable cultural shift from what we'd been used to. Since then, the profit motive has hardened further as companies have grown larger and become more corporatist. Shareholders generally have the profit motive first in mind whereas early founders of companies primarily focused on their products. This is the new norm, the current business ethic that we expect from most large corporations these days, and we have to accept the fact. It means we've now even fewer choices than ever as corporations merge and become even bigger monopolies. Therefore, like it or not, we are forced to deal with monopolistic corporations like Microsoft and they know it, they know we have to accept the limited choice they have on offer. Thus despite any utterances from its PR department to the contrary, it's clear Microsoft's whole raison d'être is aimed at maximizing shareholder profit, and if that means trampling all over users, uses' privacy and downplaying security then so be it. Right, 'business as usual needs a real change' but as things stand now there's no way that's going to happen despite Microsoft president Brad Smith's conciliatory tones. Our only hope is to force governments to act—to introduce new laws and regulations that force companies to behave responsibly. Even better would be laws that make CEOs and senior executives criminally liable for breaches of law. _ † HP is a classic illustration of the change in tech corporate ethics, these days I'd never buy any product from HP because of its unacceptable policies towards users.