Skip to content

Instantly share code, notes, and snippets.

@davepeck
Last active March 25, 2022 00:37
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save davepeck/9acdab2e8f03155094e6 to your computer and use it in GitHub Desktop.
Save davepeck/9acdab2e8f03155094e6 to your computer and use it in GitHub Desktop.

I got hit by the weird group reassignment when I upgraded to Mavericks. In my case the group was macports (!). I’ve seen one report from a user who got cloakproxy after the 10.11 upgrade, so apparently the bug is still there.

For some reason the OS X upgrader sometimes picks a group and changes the PrimaryGroupID to 20. Here’s the confirm:

dscl . -read Groups/cloakproxy
dscl . -read Groups/staff

And the fix:

sudo dscl . -delete Users/cloakproxy
sudo dscl . -delete Groups/cloakproxy

The next time Cloak is run it will re-create any needed users/groups. (If you're curious: cloakproxy is part of how our OverCloak firewalling feature works with captive portals.)

This OS X updater bug is pretty head-scratching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment