71–80 of 329 posts
Earlier quoted context omitted.
Intel has been called out by Linus Torvalds several days ago for the crappy fixes they delivered for GNU/Linux. I would be very surprised if Intel actually shipped proper fixes for Windows. It's a shame, really.
Those were not delivered fixes, that was work in progress that is still work in progress. And the dude who was "called out" works for Amazon.
I never got them. The last update in my windows is from Dec 2017. My antivirus is compliant, the registry key correctly set up and yet it refuses to update. I still haven't had the time to debug it, but I wonder how many people are out there with their OS silently refusing to update.
After probably 9 months of this, and with Windows doing ever more intrusive pop overs whenever I launched it for updates that don't take, I wiped all boot sectors everywhere and installed from scratch. That seemed to work, but it was incredibly frustrating that the boot process was so buggy as was error reporting. I've never encountered a situation like it in the past 15 years of heavy Linux use. Problems there are usually solvable with a couple web searches, even for extremely obscure kernel bugs with obscure packages. Windows refused to tell me anything as did the web.
They have handled many aspects of this issue poorly or outright incorrectly, and it is ok to expect better of a firm that profits so handsomely from this industry.
Amount of fuck-up in this whole issue is mind blowing. I am getting more surprised with every new I get
But wait, there's more! https://www.techrepublic.com/article/03175c88-5c9b-4ccd-ac62...
Earlier quoted context omitted.
Intel has been called out by Linus Torvalds several days ago for the crappy fixes they delivered for GNU/Linux. I would be very surprised if Intel actually shipped proper fixes for Windows. It's a shame, really.
Those were not delivered fixes, that was work in progress that is still work in progress. And the dude who was "called out" works for Amazon.
Earlier quoted context omitted.
Microsoft won't supply updates even if you have no AV installed, including builtin Defender disabled?? I thought stopping updates was only for the case of unpatched AVs that did not set the registry key...
If you have no patched AV, who's going to set the registry key?
So get a patched AV. If you haven't installed another AV, then Defender is there and counts.
Earlier quoted context omitted.
To force a reinitialisation of all security contexts. Same reason that many websites make you log in again immediately after changing your password (which interestingly Windows doesn’t) Historically (Windows 95 and earlier) reboots were required to reload DLLs and so on but that’s not really true anymore. Still a lot of installers and docs say to reboot when it’s not really necessary as a holdover from then
I was under the impression that the reason is what u/beagle3 mentions (in a sibling comment to yours): open system files. I'm curious to see your comment on what he describes, as what you mention (reloading some security context) does not seem to be the whole truth. That websites make one log in again after changing your password has nothing to do with this.
No it is exactly the same principle: something has changed therefore invalidate all existing contexts. Far less error prone than trying to recompute them, what happens e.g. if a resource has already been accessed in a context that is now denied? Security 101.
Gee, if only they had a Linus Torvalds type around to block irresponsible commits.
They did, once upon a time, after a fashion: https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev... https://www.wired.com/2002/01/bill-gates-trustworthy-computi...
A more accurate title would be that Microsoft disabled the specter mitigation’s due to a flawed Intel update, right? I thought this was all Microsoft’s fault until getting half way through the article.
> HP, Dell, Lenovo, VMware, Red Hat and others had paused the patches and now Microsoft has done the same.