Security Update 2017-001 BREAKS File Sharing

Discussion in 'macOS High Sierra (10.13)' started by joedec, Nov 29, 2017.

  1. joedec macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #1
    Immediately after installing this patch, file sharing fails to authenticate. I see this on multiple Macs. Hoping for some collaboration.
     
  2. bwintx macrumors regular

    bwintx

    Joined:
    Jul 17, 2002
    #2
    @joedec -- can you be a little more specific for those of us who'd like to try repro'g this issue?
     
  3. joedec thread starter macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #3
    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.
     
  4. bwintx macrumors regular

    bwintx

    Joined:
    Jul 17, 2002
    #4
    Could you provide specifics, please, to help others attempt to reproduce this?

    EDIT: Disregard. I see your reply. Sorry.
     
  5. trekkie604 macrumors 65816

    trekkie604

    Joined:
    Feb 25, 2008
    Location:
    Vancouver, Canada
  6. tkermit macrumors 68040

    tkermit

    Joined:
    Feb 20, 2004
    #6
    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
     
  7. lexvo macrumors 65816

    Joined:
    Nov 11, 2009
    Location:
    The Netherlands
    #7
    SMB file sharing is working for me (I just installed the security update).
     
  8. joedec thread starter macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #8
    You have Windows File Sharing checked right. That's a work around, a little insecure.
     
  9. lexvo macrumors 65816

    Joined:
    Nov 11, 2009
    Location:
    The Netherlands
    #9
    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.
     
  10. chrfr macrumors 603

    Joined:
    Jul 11, 2009
    #10
    I confirmed this and filed a bug with Apple on it. With luck it'll get fixed soon.
     
  11. cerote macrumors 6502a

    cerote

    Joined:
    Mar 2, 2009
    #11
    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.
     
  12. Bazonga macrumors newbie

    Joined:
    Nov 29, 2012
    #12
    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** !!
     
  13. Ries macrumors 68000

    Joined:
    Apr 21, 2007
    #13
    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.
     
  14. RyanXM macrumors member

    RyanXM

    Joined:
    Jul 7, 2012
    Location:
    DFW, TX
    #14
    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.
    --- Post Merged, Nov 29, 2017 ---
    I send an email directly to Craig Federighi. I also tweeted to @AppleSupport and @tim_cook.
     
  15. chrfr macrumors 603

    Joined:
    Jul 11, 2009
    #15
    I've already tested with an unpatched 10.13.1. File sharing works as expected there.
     
  16. Bazonga, Nov 29, 2017
    Last edited: Nov 29, 2017

    Bazonga macrumors newbie

    Joined:
    Nov 29, 2012
    #16
    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 !!
     
  17. robogobo macrumors 6502

    robogobo

    Joined:
    Jun 6, 2005
    Location:
    Sitting down facing front.
  18. haralds macrumors 6502

    haralds

    Joined:
    Jan 3, 2014
    Location:
    Silicon Valley, CA
    #18
    AFP is legacy. APFS volumes only support SMB.
     
  19. chrfr macrumors 603

    Joined:
    Jul 11, 2009
    #19
    Yes. This problem only affected SMB sharing too. AFP was unaffected.
     
  20. kagharaht macrumors 6502a

    Joined:
    Oct 7, 2007
    #20
    I just posted this. Can't access any of my shared drives anymore after this update. I have Airport AC.
    --- Post Merged, Nov 29, 2017 ---
    So after Apple updates another screw up, I wonder if this Patch will fail and we're back to no file sharing. LOL
     
  21. chrfr macrumors 603

    Joined:
    Jul 11, 2009
    #21
    Apple has revised the security update to include a script to fix this, so build number on the update is now 17B1003.
     
  22. timothevs macrumors 6502

    timothevs

    Joined:
    Nov 17, 2007
    Location:
    FL
  23. Sciuriware macrumors regular

    Sciuriware

    Joined:
    Jan 4, 2014
    Location:
    Gelderland
    #23
    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!
    --- Post Merged, Nov 30, 2017 ---
    .... insecure ... .... WHY?
    ;JOOP!
     
  24. joedec thread starter macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #24
    Good eye. I see they quietly released the new version. Fair enough, most users will never know what happened in the last 24 hours.
     
  25. solidstate94, Nov 30, 2017
    Last edited: Dec 1, 2017

    solidstate94 macrumors newbie

    Joined:
    May 24, 2017
    #25
    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.
     

Share This Page