Re:Microsoft Office 2019 will only work on Windows 10
by Silhouette on Saturday February 03, 2018 @03:43PM
(#16299527)
You don't see a moral/ethical argument for making sure your PCs don't become part of a botnet?
I don't see any evidence that giving someone who knows what they're doing the ability to control which updates they deploy and when will cause them to become part of a botnet. Are you suggesting that Windows 10 Enterprise should be similarly constrained for the same reason?
And even if systems do become part of a botnet, the correct solution to that problem is to cut off the offending systems at ISP level anyway, not to rely on their own local security in any particular respect.
But on the principle of the thing, you are being negligent
Objecting to a system that requires automated deployment of arbitrary updates, including updates that may upload arbitrary data, is not only not negligent, it may be positively required for regulatory compliance depending on your circumstances.
The anti-vaxxer parallel is extremely relevant here, if everybody thinks like that then we have a problem.
No it isn't, and this naive and superficial analogy really needs to die.
At the end of the day you're just going to have to trust Microsoft to put out good patches.
Microsoft have proved, beyond any reasonable doubt, that such trust is unjustified. Try again.
But if you don't trust them, why are you running their operating system?
Because the Microsoft of a few years ago that produced Windows 7 is a very different Microsoft to today's that produced Windows 10.
Do you have similar concerns about upstreams in the Linux community? You know patches can break things there too, right?
And yet in many years of running many systems for multiple organisations, the total downtime I have experienced due to Debian unattended security updates is 0, and the number of reports I have ever read of others suffering a bad update through that channel is also 0.
I don't see any evidence that giving someone who knows what they're doing the ability to control which updates they deploy and when will cause them to become part of a botnet. Are you suggesting that Windows 10 Enterprise should be similarly constrained for the same reason?
And even if systems do become part of a botnet, the correct solution to that problem is to cut off the offending systems at ISP level anyway, not to rely on their own local security in any particular respect.
But on the principle of the thing, you are being negligent
Objecting to a system that requires automated deployment of arbitrary updates, including updates that may upload arbitrary data, is not only not negligent, it may be positively required for regulatory compliance depending on your circumstances.
The anti-vaxxer parallel is extremely relevant here, if everybody thinks like that then we have a problem.
No it isn't, and this naive and superficial analogy really needs to die.
At the end of the day you're just going to have to trust Microsoft to put out good patches.
Microsoft have proved, beyond any reasonable doubt, that such trust is unjustified. Try again.
But if you don't trust them, why are you running their operating system?
Because the Microsoft of a few years ago that produced Windows 7 is a very different Microsoft to today's that produced Windows 10.
Do you have similar concerns about upstreams in the Linux community? You know patches can break things there too, right?
And yet in many years of running many systems for multiple organisations, the total downtime I have experienced due to Debian unattended security updates is 0, and the number of reports I have ever read of others suffering a bad update through that channel is also 0.