I guess now we get to see where all the holes in apples fucking automated tests are... meanwhile I'm happily running Arch ;)
Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
11–20 of 49 posts
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#12I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
This is why I am so glad I did not update to High Sierra. It obviously is not ready.
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#13I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
If you ship an OS that runs your premium+ pricey hardware one of the onuses on you is to be able to quickly respond to catastrophic bugs and security issues without introducing new ones.
That's why you hire best engineers, product managers and QA people and establish processes that let you do exactly that. Trouble is Apple's treating everything like toys nowadays.
Surprising though how many people are willing to give a free pass to an almost trillion dollar company.
Also you realise Apple's asking their customers to run terminal commands - even MS has fixits that just do it :)
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#14I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
If you ship an OS that runs your premium+ pricey hardware one of the onuses on you is to be able to quickly respond to catastrophic bugs and security issues without introducing new ones. That's why you hire best engineers, product managers and QA people and establish processes that let you do exactly that. Trouble is Apple's treating everything like toys nowadays. Surprising though how many people are willing to give…
What do you mean a "free pass"? Apple has been (rightly) grilled over this.
Also, though the patch does introduce this new bug, it's hardly a show-stopper, it has a simple fix, it will likely affect a tiny percentage of users, and I'm sure be resolved in a future release.
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#15I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
I feel bad for the engineers, but seriously screw Apple on this. They have an overcomplicated setup with little internal Kerberos implementations on every Mac to make peer to peer networking easier.
If it’s like everything else, it’s probably ancient and crufty. The dude who wrote it probably cashed out years ago. Some engineer rushed through and made the original worst-case-scenario error, and the guys cleaning up the mess made this error, which is understandable given the severity of the problem.
For a company like Apple that prints money, it’s irresponsible and reflective of a broken engineering process. Personally I’m angry about this because on iOS, we’re 100% dependent on their engineering process to protect my customer’s data. Hopefully that trust is well placed.
If they don’t want to maintain Macs, don’t make them.
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#16Earlier quoted context omitted.
If you ship an OS that runs your premium+ pricey hardware one of the onuses on you is to be able to quickly respond to catastrophic bugs and security issues without introducing new ones. That's why you hire best engineers, product managers and QA people and establish processes that let you do exactly that. Trouble is Apple's treating everything like toys nowadays. Surprising though how many people are willing to give…
What do you mean a "free pass"? Apple has been (rightly) grilled over this. Also, though the patch does introduce this new bug, it's hardly a show-stopper, it has a simple fix, it will likely affect a tiny percentage of users, and I'm sure be resolved in a future release.
OP did give them a pass pretty much. Also saw Jean Louise Gassee trivialize it by claiming it only affects techies looking deeper!
But ok, fair enough - I think mostly they did get grilled - just bugged me that few people found ways to justify it! :)
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#17I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
The fact they learned this only yesterday is amazingly stupid to start with. People were talking about this weeks ago on the Apple Forums, as a "neat trick" : https://twitter.com/fristle/status/935670476214378496 . Surely a moderator should have noticed something was wrong at that point. This is a major fuckup the kind of which should be illegal.
> People were talking about this weeks ago on the Apple Forums, as a "neat trick"
Aren't Apple forums mostly meant as self-help forums, with minimal monitoring by Apple?
It looks like one person posted it two weeks ago, not as a bug or security problem but as a solution to the problem that the original poster had, not realizing it was a bug. People didn't seem to notice it and start talking about it there until yesterday.
I would guess that any developers at Apple that check the developer forums just look at the first post to see what problems people are reporting, and a few of the replies to see if others are seeing the problem and see what workarounds people have found.
In this particular thread that first post was in June, and by early July someone had posted a fix. Some people had trouble with that and someone posted a more detailed fix in the middle of October.
I doubt any developers would be still following that thread on November 13th, when the root bug was posted.
As far as moderators go, I'd expect that they just skim the posts to make sure they don't violate any major rules.
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#18I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
This is why I am so glad I did not update to High Sierra. It obviously is not ready.
It's like they are the old Microsoft: never take a new version until after the first service pack.
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#19I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
High Sierra bricked my 2010 iMac.
Haven’t even bothered to try and repair it. It shipped with one of those crappy slow HD’s Apple used to save money.
Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1
#20I seriously can't imagine how much pressure engineers at Apple were to ship this patch. Considering they tend to ship infrequently, I doubt they have the sort of QA turn-around that'd support emergency releases. Remember that: - They learned about this yesterday - They had as much heads up as the general public did - They are a large company. I don't disagree that the apparent QA quality from Apple software isn't wha…
This is why I am so glad I did not update to High Sierra. It obviously is not ready.
I tried on our Mac mini servers but High Sierra won’t upgrade on a system running RAID 1. Saved some trouble today but it will be a pain if they don’t fix that bug too.