My student computers are currently on 10.11 and I was about to roll out 10.13 until the root issue showed up. Upgrading them to 10.13 and then having to push out another update to fix the root issue leaves too much of a window open for students to take advantage of the issue. Is there a way I can push out a fix while they are on 10.11 before updating them to 10.13?
Any help is greatly appreciated.
Solved! Go to Solution.
My enrolled 10.13 machines don't exhibit the flaw, I'm guessing because the enrollment settings apply a root password. I was only able to exhibit the flaw on non-enrolled machines. I would suggest testing on a non-prod machine.
@AVmcclint - I did an internet recovery on a new 2017 MBP last night and it still needed the update. Odd, but guessing it's coming in 10.13.2 as you suggested.
"release-notes" = "Security Update 2017-001 is recommended for all users and improves the security of macOS. For more information on the security content of this update see http://support.apple.com/kb/HT201222. ";