Attached: 1 image
So, Microsoft is silently installing Copilot onto Windows Server 2022 systems and this is a disaster.
How can you push a tool that siphons data to a third party onto a security-critical system?
What privileges does it have upon install? Who thought this is a good idea? And most importantly, who needs this?
#infosec #security #openai #microsoft #windowsserver #copilot
You’re not wrong, but as privacy conscious consumers we have more ways to force Microsoft and other tech giants to bend the knee than just disengaging with their product and leaving less savvy users to fend for themselves. One such example is legislative action, take a look at how the EU has been wielding their internal market to force companies into more pro-consumer practices. Another is class action lawsuits, there’s a long history of successful suits resulting in lasting change.
You might not agree with me on whether those options are the right path forward here, but I feel that we, as security and privacy conscious owners have a duty to speak up about these things for the majority that can’t or won’t due to their technical abilities.
Oh yeah, this MUST be done too, but expecting that to be the solution to MS apps getting worse all the time is for the moment not a solution for the random user of the day complaining of yet another MS enshittification escalation.
Switching to Linux gets you completely out of that mess and has lasting results, continuing to participate in the MS market might change things if the anti-monopoly forces taking encouraging actions the last few years continue advancing but will take years IF it happens, along with any class-action lawsuit, anything else in the meanwhile (patches, debloaters, secret policy rules or registry entries, etc.) is nothing more than a band-aid treating the symptoms.
So, these discussions always devolve to this because it’s a proven and effective solution that works today and lasts, unlike any other patch that can be broken next time MS forces an update or catches you unaware, it’s hard and imperfect and “not the CORRECT way to solve the problem”, but works.
You’re not wrong, but as privacy conscious consumers we have more ways to force Microsoft and other tech giants to bend the knee than just disengaging with their product and leaving less savvy users to fend for themselves. One such example is legislative action, take a look at how the EU has been wielding their internal market to force companies into more pro-consumer practices. Another is class action lawsuits, there’s a long history of successful suits resulting in lasting change.
You might not agree with me on whether those options are the right path forward here, but I feel that we, as security and privacy conscious owners have a duty to speak up about these things for the majority that can’t or won’t due to their technical abilities.
Oh yeah, this MUST be done too, but expecting that to be the solution to MS apps getting worse all the time is for the moment not a solution for the random user of the day complaining of yet another MS enshittification escalation.
Switching to Linux gets you completely out of that mess and has lasting results, continuing to participate in the MS market might change things if the anti-monopoly forces taking encouraging actions the last few years continue advancing but will take years IF it happens, along with any class-action lawsuit, anything else in the meanwhile (patches, debloaters, secret policy rules or registry entries, etc.) is nothing more than a band-aid treating the symptoms.
So, these discussions always devolve to this because it’s a proven and effective solution that works today and lasts, unlike any other patch that can be broken next time MS forces an update or catches you unaware, it’s hard and imperfect and “not the CORRECT way to solve the problem”, but works.