One step. The corps know it. It’s been happening for years. One step, then soon after you just accept that’s how it is. Then another step. And another. And another…
I think you misunderstand the relationship Microsoft has with corporations. If they turn on something like this after the fact while promising to do the opposite previously they will get thoroughly railed in court and then no one will ever buy their products ever again.
The reason that companies use Windows rather than running everything on Linux is the absolutely enormous support base that Windows has. The moment it becomes more problematic to use Windows than to just deal with the support issues of a Linux OS is the moment that everyone will switch to Linux.
Work in the space, I don’t misunderstand. Corps are one thing, what about the rest of civilization? Also some corps might even embrace as a means to spy on their employees work habits or something dystopian like that.
I actually really doubt it’d ever go on by default for enterprise installations. One tiny slipup in GPO and IT departments could end up with the most massive explicit data leak in history, many many companies and governments working with very sensitive data would drop all Microsoft products in a heartbeat. Microsoft knows that is an impossible sell and really not worth the squeeze vs just shoving a larger dildo up the private consumer’s ass.
One tiny slipup in GPO and IT departments could end up with the most massive explicit data leak in history,…
I get what you’re saying, but:
Apply this same logic to ‘Considerable and substantial direct access to the kernel for who knows how many third party software engineers, without meaningful or comprehensive review of how they’re using that access.’
Why, one serious, overlooked error on a widely used enterprise software with this kernel access could basically brick millions of business computers and cost god knows how many millions or billions of dollars, they’d never do that!
Off by default. For now…
One step. The corps know it. It’s been happening for years. One step, then soon after you just accept that’s how it is. Then another step. And another. And another…
I think you misunderstand the relationship Microsoft has with corporations. If they turn on something like this after the fact while promising to do the opposite previously they will get thoroughly railed in court and then no one will ever buy their products ever again.
The reason that companies use Windows rather than running everything on Linux is the absolutely enormous support base that Windows has. The moment it becomes more problematic to use Windows than to just deal with the support issues of a Linux OS is the moment that everyone will switch to Linux.
Work in the space, I don’t misunderstand. Corps are one thing, what about the rest of civilization? Also some corps might even embrace as a means to spy on their employees work habits or something dystopian like that.
I actually really doubt it’d ever go on by default for enterprise installations. One tiny slipup in GPO and IT departments could end up with the most massive explicit data leak in history, many many companies and governments working with very sensitive data would drop all Microsoft products in a heartbeat. Microsoft knows that is an impossible sell and really not worth the squeeze vs just shoving a larger dildo up the private consumer’s ass.
I get what you’re saying, but:
Apply this same logic to ‘Considerable and substantial direct access to the kernel for who knows how many third party software engineers, without meaningful or comprehensive review of how they’re using that access.’
Why, one serious, overlooked error on a widely used enterprise software with this kernel access could basically brick millions of business computers and cost god knows how many millions or billions of dollars, they’d never do that!
… cough CrowdStrike cough.
Microsoft Azure already leaks secrets and nobody cares. As long as it has all required certifications it’ll be fine.