Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This makes two security holes. First the blank password for root access, and this one..

I get this will be patched quickly.

My only thinking is, i am even more glad i stuck with 10.12.6.

Defiantly a steady decline. You can keep saying "its a bug" over and over to try and make it feel better, but how far can you take this before you start admitting to yourself. based on history?

At one point, you gotta start believing something else, otherwise u'r just fooling yourself.
 
I’d rather this error than Microsoft’s pulling of the Spectre and Meltdown fix update because it bricked computers with AMD chips.
Apple's released OS updates that have bricked devices, too. No one is immune.

I think it's fair to hold Apple to a higher bar - we pay for the privilege.
[doublepost=1515617681][/doublepost]
I’d rather this error than Microsoft’s pulling of the Spectre and Meltdown fix update because it bricked computers with AMD chips.
And don't forget that Apple's fix update for the prior "root password" bug also had to be pulled because it made external disks stop working.
 
"It's worth noting that the App Store preferences are unlocked by default on administrator accounts"

That's only if the user hasn't checked "Require system password" under System Preferences > Security & Privacy > Advanced.

 
Wow, Apple have become a real mess. They tout themselves as valuing user privacy and security, yet they seem to be the ones handing out the keys themselves!

Seems like they tout the privacy aspect as it applies to selling new iPhones (Face ID) and the Touchbar ID on the MBPs... and other things that sell the products they care about most. MacOS gets sent close to back of the line for Apple's priorities on really important QC such as the password debacles of late.
 
That's why I'm still on Snow Leopard in my 2008 iMac for my personal stuff at home. It barely supports today's internet. How's that for security?

:D

(It's sarcasm, or course...)
 
  • Like
Reactions: LauraJean
I'm not sure if anyone knows this but...

The current VP of Security for Apple came from Blackberry. He was the head of software operations for QNX.

Echos of the past?
 
That's only if the user hasn't checked "Require system password" under System Preferences > Security & Privacy > Advanced.
Which again is not a default setting. (It probably should be, however.)
 
Oh Boy. After the root disaster and now this I wonder what other bugs under the hood there are. And they are probably much more serious than this.
 
  • Like
Reactions: idunn
And people trust Apple to design secure ARM processors?!

They're basically as bad as Intel with these breaches.... first the root one now this :D
 
  • Like
Reactions: idunn
Yes and that error happened because AMD provided Microsoft with the wrong documentation about those CPU's. It is always easy to blame Microsoft first I suppose.

Yes. That was an AMD cockup not Microsoft.

I don't trust AMD. One of my graphics chips died in a laptop and an ATI disk controller gave up the ghost. Shoddy and in my experience; Drivers are poor as well. Wouldn't touch them with a bargepole.
 
  • Like
Reactions: AndyMacAndMic
Yes and that error happened because AMD provided Microsoft with the wrong documentation about those CPU's. It is always easy to blame Microsoft first I suppose.
It is always easy to blame other for Microsoft’s mistake I suppose. Apple doesn’t push updates to devices their updates aren’t designed for.
 
It is always easy to blame other for Microsoft’s mistake I suppose. Apple doesn’t push updates to devices their updates aren’t designed for.

I repeat: AMD gave Microsoft the wrong information about those CPU's.

What is there not to understand? Microsoft can't possibly test all the configurations and devices Windows is running on. Apple can because they provide the hardware and the software.
 
It is always easy to blame other for Microsoft’s mistake I suppose. Apple doesn’t push updates to devices their updates aren’t designed for.

It's not Microsoft's job to babysit AMD if they don't even know THEIR OWN PROCESSOR SPECS.

After investigating, Microsoft has determined that some AMD chipsets do not conform to the documentation previously provided to Microsoft to develop the Windows operating system mitigations to protect against the chipset vulnerabilities known as Spectre and Meltdown.

https://www.google.co.uk/amp/s/arstechnica.com/gadgets/2018/01/bad-docs-and-blue-screens-make-microsoft-suspend-spectre-patch-for-amd-machines/?amp=1
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.