Date
1 - 2 of 2
Where does one place system-wide user binaries?
Carl Hoefs
macOS 12.5.1, M1 Max, Xcode 13.4
My Foundation-based daemon binary runs fine within Xcode and in my own local directories, but when I try to place it into /opt/local/bin or /usr/local/bin, macOS SIP won't let it run from there:
proc 20514: load code signature error 2 for file "simprefix"
ASP: Security policy would not allow process: 20514, /usr/local/bin/simprefix
proc 20598: load code signature error 2 for file "simprefix"
ASP: Security policy would not allow process: 20598, /opt/local/bin/simprefix
Is there some attribute I'm supposed to grant the binary so it can be run?
-Carl
My Foundation-based daemon binary runs fine within Xcode and in my own local directories, but when I try to place it into /opt/local/bin or /usr/local/bin, macOS SIP won't let it run from there:
proc 20514: load code signature error 2 for file "simprefix"
ASP: Security policy would not allow process: 20514, /usr/local/bin/simprefix
proc 20598: load code signature error 2 for file "simprefix"
ASP: Security policy would not allow process: 20598, /opt/local/bin/simprefix
Is there some attribute I'm supposed to grant the binary so it can be run?
-Carl
On Sep 23, 2022, at 4:10 PM, Carl Hoefs <newslists@...> wrote:My Foundation-based daemon binary runs fine within Xcode and in my own local directories, but when I try to place it into /opt/local/bin or /usr/local/bin, macOS SIP won't let it run from there:
Usually these are part of an application and bundled inside it. Or you could put it in /Library/ApplicationSupport (or ~/Library/…)
You also have a launchd plist for this, right?
—Jens