Network shares seems to be the initial thing. Who knows what else? Anything requiring root daemon startup authentication? Perhaps email tcook and ask him?Actually, quite the opposite.
On a different note, what is this fix going to break?
Network shares seems to be the initial thing. Who knows what else? Anything requiring root daemon startup authentication? Perhaps email tcook and ask him?Actually, quite the opposite.
On a different note, what is this fix going to break?
My understanding is that the fix disables any root access that exists, via the temp fix or otherwise. You will proactively have to reestablish root access if you actually want it (the temp fix, as we're calling it, is actually the standard method that is normally required.) For almost everybody, that's a no.Now that this fix is out, what is the best security setup for dealing with root access: keep it on with a strong password (ala the temporary fix) or turn it off?
lol hilarious
Wrong.
What wouldn't be a "good look" would be to do what MS does:
1. Deny the error for two weeks.
2. Blame the User for another two weeks.
3. Issue a patch.
4. Deny the error that the patch creates for a month.
5. Blame the User for the error that the patch creates for another month.
6. Quietly issue a patch at their next regularly-scheduled Patch Tuesday.
Time for Apple to admit, apologize, and fix the original error: < 24 hours.
Time for Apple to fix the patch: < 12 hours.
Get over it.
[doublepost=1512037774][/doublepost]
As I said above, I write software for a living, and I have a longstanding phrase:
"Fix a bug, make a bug".
Happens.
[doublepost=1512037833][/doublepost]
Give it a rest.
[doublepost=1512037911][/doublepost]
Both High Sierra and iOS 11 had Public Betas for months.
So WHO didn't bother to check things?
Would you rather that they took an extra week to develop and test a GUI solution for a two-second fix?
[doublepost=1512038338][/doublepost]
...Not that it is any better in Windows...
Indeed!
[doublepost=1512038545][/doublepost]
It's not an "approach"; it's a FACT.
And the "QA Team" doesn't get a chance to sign-off in an emergency situation like this.
[doublepost=1512038788][/doublepost]
Um, it was.
But then, BECAUSE OF THE INSTANTANEOUS RELEASE, there was an UNINTENDED CONSEQUENCE.
But, nobody lost any data.
The fix for the fix was pretty simple.
And Apple released that fix in < 12 hours.
You OBVIOUSLY have never written a byte of code in your life. I make my living doing just that.
[doublepost=1512038919][/doublepost]
Then go to Windows or Linux for some REAL "Customer Support".
We'll wait...
[doublepost=1512039032][/doublepost]
Compared to what, exactly?
[doublepost=1512039444][/doublepost]
Who says they won't?
[doublepost=1512039742][/doublepost]
What now?
Apply the simple fix and be happy.
https://support.apple.com/en-us/HT208317
SECOND Security Update!
Apple published another update some minutes ago.
My advice: Restart your machine after the update! Check the build number in "About this Mac" (click on 10.13.1). Is it 17B1003 (after the second update)? If not: Start your machine new. You'll encounter a "Setting up your Mac" routine when it starts (pretty unusual for a "normal" restart).
Here—MacBook Pro (15-inch, Late 2016)—it was 17B48! Only after the restart it was 17B1003!! I hope Apple didn't forget that after the update a restart is obligatory! After both updates a restart was not required by default. (Or it's just the build number which is flawed. Confused.)
Btw when you installed the first security update only the build number should be 17B1002.
Attachment (screenshot): Both updates in the "recent updates" list in Mac App Store (German-language).
Edit: A buddy told me that it isn't necessary to restart the machine for being able to see the most recent build number. BUT you have to close and open again the "About this Mac" window. I can't verify this right now. Please restart your machine anyway.
Not sure what variables were for you but - just did a clean install of High Sierra (from Sierra) and my boot time is faster than ever, under 10 seconds as well. Sort of spooked me, Sierra was slower than El cap for me.
Are you using an HDD or SSD? Did you upgrade or do a complete wipe and install, without restoring from backup?
Really?
REALLY?
If they "Gave zero craps about the Mac", they wouldn't have fixed the Root authentication issue in less than 24 hours, and they wouldn't have fixed this unintended consequence in less than 12 hours after that.
EVERYone has bugs. It's how you DEAL with them that counts.
If you wrote software for a living (like I do), you'd understand that.
I saw that too but a reboot seems to have taken out a few "hesitations" after mouse clicks, scrolling etc. It seems to have helped somehow. But no, Safari is not snappier. LOLI just got the second update here also and am now sitting at macOS 10.13.1 (17B1003) without a reboot.
Time for Cook to resign. His tenure has been a disaster.
I can’t disagree more.
Does it disturb anyone else but me that apple can install something on my computer without my permission?
The cool aid is strong with you.
“give it a rest” LMAO..... you should get over yourself buddy.
Again, get over yourself.
So what if someone has never written a line of code in their life? People who pay premium prices for their devices expect a premium product, that includes hardware, software, customer service and support.
Why are you IGNORING the fact that the issue was first mentioned two weeks ago? Apple only rolled out a desperate fix once the media started reporting it.
People like you who accept inferior products and services as PREMIUM are the reason Apple are on a downwards trend in quality, design and innovation.
This security issue is just a small issue in the overall picture, it is one more symptom in the trillion dollar company that is slowly turning into the next Blackberry.
I am able to enjoy my Apple products without believing they are deities that do no wrong.
Did you read the small print?Does it disturb anyone else but me that apple can install something on my computer without my permission?
Do you have any proof to back the statement that this issue was first mentioned two weeks ago? (no sarcasm intended)
Regarding "hardware, software, customer service and support", I pay premium and I get just that. This comes from a person which makes a living using their machines with 99.9% uptime and reliability since day one.
Don't get me wrong, Apple really should realise the fact that we use their platforms because the others ones are inferior.
Different users have different needs, but in high-end audio, Windows and Linux are a complete hassle.
Yes, I can see them now, adopting Android and respectively Windows on their devices because iOS 11 and OS X have bugs!
I know that this sounded like a good ending sentence to your very convincing post, but you actually managed to contradict yourself.
There are worse products out there that charge premium and disappoint. Take a look at Samsung, Dell, Microsoft, Lenovo, just to name a few. Lenovo actually had spyware bundled with the preinstalled OS.
Back to my point, different users require different solutions. This is like '98 and '05 all over again. Get over yourself, buddy.
You're obviously crazy, Cook's only made Apple the most valuable brand in the world, made iPhone the most popular phone in the world, made Apple Watch (and smartwatches in general) ubiquitous, and made investors wildly wealthy! He's clearly terrible for the company, and must go now!/s
Sorry, you’re wrong. Not “internS”, but like the original post: “intern”Apple please fire the interns incharge of macOS and iOS. iOS 11 and macOS High Sierra have been a disaster.
How about Apple fixing the Server 5.4 version? I am getting temporary Office 2016 folders created anytime my users open a document (word, excel) and saving them. This is via SMB. By the end of the day there are tons of useless folders that I have to go in and delete!!
I will have to spend this weekend to downgrade everything back to an older version.
He had a tough act to follow.Time for Cook to resign. His tenure has been a disaster.