If MacOS users run this one line before installation, they can avoid the whole "unverified binaries" error.
The following situation exists for MacOS users:
download Ghidra zip file from GitHub using Safari or Chrome
use unzip or the MacOS archive to unpack the zip file
later, when Ghidra runs the demangler, decompiler or other prebuilt binaries, they get an error like:
"demangler_gnu_v2_24" cannot be opened because the developer cannot be verified"
MacOS is doing what it should. Browsers (like Safari/Chrome) mark downloaded zip files with the "com.apple.quarantine" extended attribute. On unpacking, programs like unzip or MacOS archive (but not tar) then mark all files within with that flag. MacOS blocks running those binaries, causing decompilation, etc to block.
Yes, the user can go to Preferences->Security & Privacy and allow the override. This is awkward because you need to go through this process for each time a new binary is encountered.
Removing the com.apple.quarantine attribute on the zip file before unpacking solves all of this.
If MacOS users run this one line before installation, they can avoid the whole "unverified binaries" error.
The following situation exists for MacOS users:
MacOS is doing what it should. Browsers (like Safari/Chrome) mark downloaded zip files with the "com.apple.quarantine" extended attribute. On unpacking, programs like unzip or MacOS archive (but not tar) then mark all files within with that flag. MacOS blocks running those binaries, causing decompilation, etc to block.
Yes, the user can go to Preferences->Security & Privacy and allow the override. This is awkward because you need to go through this process for each time a new binary is encountered.
Removing the com.apple.quarantine attribute on the zip file before unpacking solves all of this.