The link provided clearly says released 6th December 2017. Unless I’m reading it wrongThe link provided shows no download for the update, let alone anything in the App store. So it can not be said that it has been "released". Released is exactly that; released to be downloaded. Announced is a different thing. It has been announced, not released.
BL.
The link provided shows no download for the update, let alone anything in the App store. So it can not be said that it has been "released". Released is exactly that; released to be downloaded. Announced is a different thing. It has been announced, not released.
BL.
what is that wallpaper on those Macbooks?
The fixes were indeed backported to Sierra and El Capitain in the Security update.
It is very clear that the mitigation was part of the security patches released last month. It simply wasn't made public as the flaw was still a secret at that point. Some relief as I'm still on El Capitan.
macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan
OS X El Capitan 10.11.6, macOS Sierra 10.12.6, and macOS High Sierra 10.13.1
6 Dec 2017
This document describes the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan.
Kernel
Available for: macOS High Sierra 10.13.1, macOS Sierra 10.12.6, OS X El Capitan 10.11.6
Impact: An application may be able to read kernel memory
Description: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.
CVE-2017-5754: Jann Horn of Google Project Zero, Werner Haas and Thomas Prescher of Cyberus Technology GmbH, and Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from Graz University of Technology
Entry added January 4, 2018
not that i am one of those guys who complain but this is a bad example. Companies knew about this issue since very long time. 9th of Jan was coordinated publishing date but because of news leaks **** hit the fan before this date. So not quick in anywayThat was quick. And yet there were still many crying "Why won't Apple be more open and talk about this!!!!"
Thank you for going some way to clarifying this if it is indeed the relative fix. Apple should be more transparent when issuing fixes for older releases. But what of Yosemite?It is very clear that the mitigation was part of the security patches released last month. It simply wasn't made public as the flaw was still a secret at that point. Some relief as I'm still on El Capitan.
macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan
OS X El Capitan 10.11.6, macOS Sierra 10.12.6, and macOS High Sierra 10.13.1
6 Dec 2017
This document describes the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan.
Kernel
Available for: macOS High Sierra 10.13.1, macOS Sierra 10.12.6, OS X El Capitan 10.11.6
Impact: An application may be able to read kernel memory
Description: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.
CVE-2017-5754: Jann Horn of Google Project Zero, Werner Haas and Thomas Prescher of Cyberus Technology GmbH, and Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from Graz University of Technology
Entry added January 4, 2018
My thoughts exactly, I thought that spectre was demonstrated on ARM. All these companies and journalists are contradicting themselves. I imagine there is still a lot of ongoing work and not everything has been made public and clearly not enough coordination amongst the researchers and companies. Seems like everyone is scrambling to get in front of the press.
Actually, Microsoft released first patches on Windows Insider in November and they've been benchmarking the performance since then. Only the official release got out yesterday.So typical of Apple to be ahead of the game like this. They already fixed most of the bug issue with Mac OS 10.13.2, which was released on December 6th, and will complete patches on 10.13.3. They were a month ahead of the press releases when this Intel "bug" issue became public. Microsoft rushed to release a patch yesterday evening, whereas Apple were comfortably ahead of it all. I have updated to 10.13.2 and have not experienced any performance decreases with my six year old MacBook Pro. Apple has done great with keeping their products number 1. Now the question to be asked is will Apple begin using AMD processor chips rather than Intel because of all of this negative publicity toward Intel.
These security flaws are gonna cause the biggest OSes version fragmentations in the history of Apple. Mark my words. People's thoughts are going to be something like this: "If I'm screwed up no matter what super new technology I have. Safe computing and to hell with everything else" (Just my thought)![]()
my question is where do I get those wallpapers?
I wonder if this explains why after the latest update for El Cap that my 15-inch MBP (Haswell CPU) was running hotter and noticeably slower, especially when virtualizing? I ultimately wound up doing a carbon clone restore to an OS backup I made before the update was installed.