Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I think the "half baked" and "broken" references may have been added to assist with attaining some sense of superiority. The "3 weeks old" reference has to do with how long 10.13.1 has been out (?), and therefore, how long the vulnerability has existed. It did not become a vulnerability because it was announced yesterday.

Actually looking at links above @Westside guy posted a link to a discussion a few weeks ago on the Apple dev forum where the issue was discussed but people didn't really seem to have a handle on it. Interesting.

Meanwhile @tkermit link above shows a new discussion here saying AFP file sharing is not working for a couple of users, including him/herself.
 
  • Like
Reactions: macfacts
We the consumers? I’ve been a Mac user for 28 years.

You realize this company went from a base of hundreds of thousands of users to over a BILLION right?

I’m hoping you grasp mathematics. More users bring more implications of the potential for trillions of more errors and conflicts. Name a company with the kind of growth Apple has gone through and seemingly would be able to micromanage every single potential software conflict...that might exist.

Right?

The software is the software, whether there 2 users or 2 million. Your logic defies reasoning.
[doublepost=1511979372][/doublepost]I really feel these glaring software bugs are endemic of an industry that is using automated testing more in lieu of human testers.
 
  • Like
Reactions: daveak and arkitect
Apple today released Security Update 2017-001 to fix a serious vulnerability that enables access to the root superuser with a blank password on any Mac running macOS High Sierra version 10.13.1.

I've completed Apple's Security Update (as of this writing).

Followup question: 's SU Support page seems to imply completing this SU (to the new 10.13.1 Build) disables root. ...Is this correct? ...If yes, does this delete a prior root PW & is it recommended to re-enable root, re-setting a PW?
 



Apple today released Security Update 2017-001 to fix a serious vulnerability that enables access to the root superuser with a blank password on any Mac running macOS High Sierra version 10.13.1.

rootbug.jpg

The critical bug, which gained attention after it was tweeted by developer Lemi Ergin yesterday, lets anyone gain administrator privileges by simply entering the username "root" and a blank password in System Preferences > Users & Groups.

The security update is rolling out on the Mac App Store now, and it should be installed by all users running macOS High Sierra as soon as possible. Regardless, starting later today, Apple said the security update will be automatically installed on all Macs running macOS High Sierra 10.13.1.

Apple has since apologized for the vulnerability in a statement obtained by MacRumors:The vulnerability does not affect macOS Sierra or any other previous version of the operating system.

Article Link: Apple Releases macOS High Sierra Security Update to Fix Root Password Vulnerability
10.13.2 beta 5 is still open, no patch.. even as it was update like 12 h ago
 
It boggles the mind that everyone seems to forget that Jonny Ive was put in charge of software after they canned Forestall on trumped up nonsense, only recently was Ive finally replaced by Craig.

All the garbage software Apple has released for the past 5 years is Ive's fault, he doesn't know software and he's no manager by a long shot.
Ive was never put in charge of software engineering. When Scott Forestall left iOS engineering teams moved under Craig Federighi who already was in charge of macOS engineering.
 
  • Like
Reactions: decafjava
I've completed Apple's Security Update (as of this writing).

Followup question: 's SU Support page seems to imply completing this SU (to the new 10.13.1 Build) disables root. ...Is this correct? ...If yes, does this delete a prior root PW & is it recommended to re-enable root, re-setting a PW?

Best leave it disabled.
 
  • Like
Reactions: BlueBook
Nobody using a public beta is concerned with security.

What an ignorant statement. As a registered developer, believe me, I'd like nothing more than to be running the non-beta version. The only reason I'm running the beta right now is out of necessity, to provide sysdiagnose dumps to Apple in the hopes that they'll fix an incredibly annoying bug introduced by High Sierra that's causing a 70% hit to discrete GPU compute performance any time a 2016/2017 MacBook Pro has entered sleep long enough to enter standby (which is resulting in me having to restart High Sierra several times a day if I want to get any work done):

https://forums.macrumors.com/thread...ot-work-after-resume-from-long-sleep.2076334/

You wouldn't believe the hours I've wasted running "sudo sysdiagnose", installing logging profiles and uploading GBs of files to bugreport.apple.com since September. High Sierra is a hot mess. The least Apple could do, if they introduce a shoddy OS release that happens to also contain serious security flaws like this, is push out an update to the users who are helping them find and fix the bugs (whether they want to be or not).
 
Until now, I didn't even know MacOS has a restartless mechanism for quick security updates. Clearly Apple anticipated a fix like this being necessary in advance ;)
I wonder if Apple being able to quietly force updates onto deployed Macs is in itself a security/privacy concern? It could mean Apple potentially being able to force a change on the OS anytime they wanted to, perhaps some third-party actor might be able to take advantage of that update system or that a government could compel Apple to use that update system to make changes to users computers.
 
Oh!!! Apple could have fixed it two weeks ago. What have they been doing? Designing new animoji?

That's the problem though. It wasn't reported. There was a discussion on the dev board where the guy stumbled upon a solution on another board (which means it was known elsewhere) to give himself back admin access but, by his own admission he didn't know this was an issue

That guy said:
Didn't realise this was a full blown security issue. I'd messed my login credentials trying to change my apple id and voila I was no longer an admin.

Then began my extensive search on all Apple related forums for a solution. Tried everything, didn't work.



As to how I stumbled on this, the answer is simple. Pure frustration. I'd read on one of the forums where in a user suggested we try using "root" for username and leaving the password field empty. I did, it failed. Out of sheer frustration, I tried again, and voila the **** thing unlocked my admin account much to my relief.



Then I posted it here assuming someone stuck just like me might find it useful. It was purely accidental.
 
I think the bug was reported two weeks ago: https://forums.developer.apple.com/thread/79235#277225

So Apple had enough time (over Thanksgiving) to solve the vulnerability. It became public as late as yesterday. I'm curious whether the problem persisted/persits with the current macOS beta.

That was a post offering the “bug” as a solution to an issue another developer was having on those forums. It was not an official bug report. In fact, the person that posted that didn’t even know it was a bug (ie: “No idea how or why it works, but it does”.)

Bugs are reported using a standard, documented procedure, which was not at all followed in that post to which you are referring: https://developer.apple.com/bug-reporting/
 
  • Like
Reactions: sunny2k1
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.