Security Update 2017-001 BREAKS File Sharing

joedec

macrumors 6502
Original poster
Jul 25, 2014
405
25
Cupertino
Immediately after installing this patch, file sharing fails to authenticate. I see this on multiple Macs. Hoping for some collaboration.
 

joedec

macrumors 6502
Original poster
Jul 25, 2014
405
25
Cupertino
@joedec -- can you be a little more specific for those of us who'd like to try repro'g this issue?
With the Finder open a file share to any Mac with the security update installed. Status shows "not connected", when you try to "connect as" your username and password fail.
 
  • Like
Reactions: bwintx

bwintx

macrumors 6502
Jul 17, 2002
325
230
Immediately after installing this patch, file sharing fails to authenticate. I see this on multiple Macs. Hoping for some collaboration.
Could you provide specifics, please, to help others attempt to reproduce this?

EDIT: Disregard. I see your reply. Sorry.
 

tkermit

macrumors 68040
Feb 20, 2004
3,438
2,445
Having the same issue since I've applied the patch. Interestingly, I had previously experienced this at some point running a beta version of 10.13.1.

What works for me is to activate Windows File Sharing for the account, but that seems like an insecure workaround.

fs.png
 
  • Like
Reactions: joedec

lexvo

macrumors 65816
Nov 11, 2009
1,241
398
The Netherlands
You have Windows File Sharing checked right. That's a work around, a little insecure.
I just now realise that I only have SMB connections from my Mac to my NAS, not to my Mac (and I don't have Windows File Sharing checked). I missed this in your second post, sorry for the confusion.
 

cerote

macrumors 6502a
Mar 2, 2009
835
267
I had issue after changing password for root last night. When I copied some files from my NAS to iMac they all were permission locked.
 

Bazonga

macrumors newbie
Nov 29, 2012
11
8
Confirming the issue. I can't acces my mac through local network anymore. Worked fine before the update. SMB sharing is activated, but get no access with user/password. Drop Box - folder is unusable as well, even for guest account, writing to that folder is not working as well. I guess Apple messed it up again.
..."as soon as possible" ... my a** !!
 

Ries

macrumors 68020
Apr 21, 2007
2,182
2,567
I wonder if Apple developers are measured on bugs closed... It's almost like they only fix and test what the bug report entails, **** wondering what the fix affects and testing the rest of the system, like it would cost them time and lower their score. PKI sucks for developers, because it always ends in min/max behaviour, not whats best for the project.
 

RyanXM

macrumors 6502
Jul 7, 2012
393
399
DFW, TX
To be a little more accurate: this breaks File Sharing between High Sierra machines that have the update installed.

I can file share to a Mac mini running 10.12.6 (fully updated) just fine. If I try to file share to any High Sierra machine from the Mac mini, credentials are rejected. This is simply an issue with the Security Update. I currently have a fresh install of 10.13.1 going on a test machine to narrow it down to the Security Update 2017-001 for 10.13.1.
[doublepost=1511995139][/doublepost]
I confirmed this and filed a bug with Apple on it. With luck it'll get fixed soon.
I send an email directly to Craig Federighi. I also tweeted to @AppleSupport and @tim_cook.
 
  • Like
Reactions: Bazonga

chrfr

macrumors G3
Jul 11, 2009
9,250
3,205
I can file share to a Mac mini running 10.12.6 (fully updated) just fine. If I try to file share to any High Sierra machine from the Mac mini, credentials are rejected. This is simply an issue with the Security Update. I currently have a fresh install of 10.13.1 going on a test machine to narrow it down to the Security Update 2017-001 for 10.13.1.
I've already tested with an unpatched 10.13.1. File sharing works as expected there.
 

kagharaht

macrumors 6502a
Oct 7, 2007
893
386
I just posted this. Can't access any of my shared drives anymore after this update. I have Airport AC.
[doublepost=1512011115][/doublepost]
ok guys, here's the fix from apple for file-sharing trouble https://support.apple.com/en-us/HT208317

entering sudo /usr/libexec/configureLocalKDC into terminal should repair file-sharing.

tested and confirming filesharing works again !!
So after Apple updates another screw up, I wonder if this Patch will fail and we're back to no file sharing. LOL
 

Sciuriware

macrumors 6502
Jan 4, 2014
356
36
Gelderland
Yes. This problem only affected SMB sharing too. AFP was unaffected.
2 weeks ago I swapped AFP for SMB. This week I did not have a single problem with
File Sharing between my 3 macs, not before - not between those updates, not after.
What did I do wrong? (LOL)
;JOOP!
[doublepost=1512056864][/doublepost]
Having the same issue since I've applied the patch. Interestingly, I had previously experienced this at some point running a beta version of 10.13.1.

What works for me is to activate Windows File Sharing for the account, but that seems like an insecure workaround.

View attachment 739136
.... insecure ... .... WHY?
;JOOP!
 

joedec

macrumors 6502
Original poster
Jul 25, 2014
405
25
Cupertino
Apple has revised the security update to include a script to fix this, so build number on the update is now 17B1003.
Good eye. I see they quietly released the new version. Fair enough, most users will never know what happened in the last 24 hours.
 
  • Like
Reactions: solidstate94

solidstate94

macrumors newbie
May 24, 2017
4
0
Good eye. I see they quietly released the new version. Fair enough, most users will never know what happened in the last 24 hours.
Was wondering why the 2017-001 update message showed up again in the App store. I installed the original 2017-001 update and it was successful. In fact, my build number is 17B1002.

From another forum I read that since the build number changes as chrfr pointed out, the Nvidia driver (Macs that use this driver) gets disabled. Correct me if I am wrong.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.