But if you're on the public beta it appears you're out of luck... hopefully they push a fix out for that as well.
Nobody using a public beta is concerned with security.
But if you're on the public beta it appears you're out of luck... hopefully they push a fix out for that as well.
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, SMB file sharing (with the Windows File Sharing option disabled) is what doesn't appear to work.Meanwhile @tkermit link above shows a new discussion here saying AFP file sharing is not working for a couple of users, including him/herself.
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?
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.
10.13.2 beta 5 is still open, no patch.. even as it was update like 12 h ago
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.
![]()
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
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.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.
Do you lose pay if you did something wrong at work?Does Craig loose some stock options for this and other software bugs that seem to become more prevalent with Apple software?
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?
Specifics are fun.Damn it, you're right
Nobody using a public beta is concerned with security.
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.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![]()
The former, i.e. shares residing on a 10.3.1 machine post-patch. Specifically SMB shares for user accounts without Windows File Sharing enabled. @joedec has created a thread that discusses the issue.Specifics are fun.
Are you referring to shares residing on a 10.13.1 machine, or shares residing on other machines?
Nothing for me on the 10.13.2 beta.
That was quick
Does anyone have the link to download the file .pkg for mass deployment?
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.
Employees often get fired if they do something wrong.Do you lose pay if you did something wrong at work?
Oh!!! Apple could have fixed it two weeks ago. What have they been doing? Designing new animoji?
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.
The extremely highly paid employees are taking their money and enjoying life instead of constantly sitting in front of the computer. They are walking around the Apple Park enjoying the trees and water fountains.WTF is going on at Apple that this sort of vulnerability slips through?