Skip to main content

Dear fellow mac admins,

Over the last couple of days we've seen a sad (but probably sound) development in AFP auto-mounting volumes via script.

macOS security patch 2018-006 has broken most of our nice little auto-mounting scripts for customers, throwing pre-populated login-box rather than mounting the file share and volume.

Prerequisites for this to work has been that the users AFP-credentials has been present in the keychain, which in turn allowed for

#!/bin/sh
open afp://server-fqdn/share

to be run by a script (with some error handling and checking beforehand).

This patch is applied all the way down to macOS 10.12 at least, and the way we're about to circumnavigate it is with by building, signing and TCCing (verb?) a wee .app.

Testing done so far with outcome:

macOS 10.14.1 (18B75):
open afp://server-fqdn/share - without keychain item:
prompted for login.
Arrives at 'Select the volume' window regardless of specified absolute path

open afp://server-fqdn/share - with keychain item:
not prompted for login.
Arives at right volume

macOS 10.12.6 (16G1710) (This is 10.12.6. with 2018-006 applied):
open afp://server-fqdn/share - without keychain item:
prompted for login
Arrives at 'Select the volume' window regardless of specified absolute path

open afp://server-fqdn/share - with keychain item:
prompted for login. Details pre-filled
Arrives at 'Select the volume' window regardless of specified absolute path

macOS 10.14.2 (18C54):
open afp://server-fqdn/share - without keychain item:
prompted for login
Arrives at 'Select the volume' window regardless of specified absolute path

open afp://server-fqdn/share - with keychain item:
prompted for login. Details pre-filled
Arrives at 'Select the volume' window regardless of specified absolute path

Any similar experiences, comments, cooler workarounds than ours?
Happy for any inspiration/feedback.

Thanks!

I can confirm that everything is working as usual with the 10.14.3 update. I have not yet tested 2019-001 for Sierra and High Sierra yet though.


Yup, those fixed it. Thanks again.


@janselmi3953 I'm seeing 2019-001 fix the issue for High Sierra


I'm seeing these issues again with Sierra 2019-002 and High Sierra 2019-002. Submitted a bug report on the topic.


@cizdziem seeing the same. Do you have a Radar# to duplicate?


49294440, sorry, that would've been good info to include in my post yesterday!


We have seen the same issue on both High Sierra and Mojave and were told by Apple that it is a bug. The 10.14.3 update fixed the issue in Mojave for us. We use an update server for all of our Apple updates, and I disabled the security update on High Sierra to stop it from happening on those Macs. It has been successful so far.

Our solution to our users is to either use our Erase/Install policy to "reimage" their Mac to High Sierra without that update, or wait till we have a Mojave upgrade available.


This seems to be fixed in the re-released updates
https://support.apple.com/en-us/HT209635