Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

support.apple.com

Post reply on HN
Print view View original

21–30 of 49 posts

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#21

Post by digi_owl »

Spooky23 wrote: post #15
bichiliad wrote: post #9

I 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 t…

It seems that whenever one attempts to make something easier on the surface, the complexities underneath expand cubically.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#22

Post by mc32 »

ams6110 wrote: post #18
apostacy wrote: post #12

Earlier quoted context omitted.

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.

It's been that way for macOS since Leopard. They'd introduce regressions all the time --and their SMB client is awful. Never trusted it till like a .3 version.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#23

Post by mberning »

From a quality standpoint Apple is a shadow of its former self. For me a large number of the more recent features in macOS and iOS don’t work reliably. Things like handoff, text message forwarding, enabling tethering from the Mac, etc. are 50/50. These kind of things used to be Apples bread and butter. Taking ideas like these and making them “just work”. And now the security regression are creeping in. I would love to see them get back to very simple product lines and a more minimalist approach to software features.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#24

Post by szc »

Spooky23 wrote: post #15
bichiliad wrote: post #9

I 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 t…

I designed and implemented quite lot of the LocalKDC mechanism - um, roughly about 11-12 years ago now I think. At the time it was based on the MIT version of Kerberos. When Apple switched to using Heimdal, the LocalKDC implementation was updated and it has been maintained since then - I am no longer the maintainer of this software. I haven't cashed out.

As to why the LocalKDC exists? How can you do secure peer-to-peer authentication without relying on some sort of global (and broken) or private PKI infrastructure? SRP wasn't an option at the time.

I am sorry you are upset. Apple is really, really serious about protecting customer data. I encourage the reading of the Apple iOS Security Guide - it describes hardware and software techniques used to protect your data. There is also the 2016 Blackhat presentation by Ivan Krstic that gives more insight into the Secure Enclave.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#25

Post by natch »

melling wrote: post #19
bichiliad wrote: post #9

I 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.

Expecting a 2010 Mac to work with 2017 software (which I infer from your bothering to post here) seems a bit of a stretch. And all hard drives were slow back then. Any variance between models then is lost in the noise when comparing against SSDs, which were not generally available in 2010.

But it should definitely refrain from bricking the machine... that’s a bummer.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#26

Post by LCDninja »

Seriously!

I can’t even install 10.13.1 on my Mac Pro 2013 - computer acts like its bricked until rebooted a number of times (and when it finally boots we’re back at 10.13).

This also means I can’t install the latest security update that fixes the root problem (and yes, i’ve changed the root password to mitigate).

OSX is becoming more like Windows every day.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#28

Post by GirlsCanCode »

digi_owl wrote: post #21
Spooky23 wrote: post #15

Earlier quoted context omitted.

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 t…

It seems that whenever one attempts to make something easier on the surface, the complexities underneath expand cubically.

Exactly. And the old K&R Unix that sits beneath it all may have been stretched to its limits. Time to switch to a modern operating system with a proper security model.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#29

Post by k_sze »

The article says “if file sharing doesn’t work”, but is it ok to just run this command line fix anyway?

I’m not sure if file sharing is broken for me. I don’t use it right now. But I’m afraid I might run into this bug in the future when I eventually use file sharing, and then I will have forgotten about this fix, and end up spending hours scratching my head and head-desking.

Re: Repair file sharing after Security Update 2017-001 for macOS High Sierra 10.13.1

#30

Post by masterleep »

mberning wrote: post #23

From a quality standpoint Apple is a shadow of its former self. For me a large number of the more recent features in macOS and iOS don’t work reliably. Things like handoff, text message forwarding, enabling tethering from the Mac, etc. are 50/50. These kind of things used to be Apples bread and butter. Taking ideas like these and making them “just work”. And now the security regression are creeping in. I would love t…

Handoff is definitely a weird one. I don't think I've ever gotten it to do anything useful. Its functionality is seemingly limited to popping up a random icon to the left of the dock from time to time to distract me.
Post reply on HN