v4.9.2 Quarantine of FileBot.app issue... anyone else?
Posted: 25 Sep 2020, 16:50
I am using the FileBot beta version downloaded via homebrew (not the MAS version) and I get a warning each time I run FileBot. Allowing the app to bypass Gatekeeper using Admin credentials doesn't change this because the FileBot.app has a quarantine flag set. I am unsure why. Anyone familiar with this?? I did find a few articles:
how-macos-overrides-app-behaviour-including-quarantine
quarantine-apps
In the past on macOS once you have approved an app that is from an "unidentified developer" the system will keep a record of that exception and stop pestering you with warnings. This doesn't work with the homebrew installed version of FileBot. I am assuming because it's not signed at all? (although other unsigned applications installed with homebrew don't exhibit this behavior)
These are the typical windows we are used to, but allowing this app to run once doesn't resolve the warning for the second launch because it has a quarantine flag set.
To make sure gatekeeper's list of overrides includes my new exception for FileBot.app:
That shows the override rule was indeed created. Yet each time I launch FileBot.app I get the same warning.
Checking to see if the application is signed shows that it is not signed.
Checking to see if this app is quarantined shows it was.
I removed the quarantine attribute using this command:
Now FileBot runs without warning me that it "is an application downloaded from the internet." Except whenever I update the beta I will need to perform this dance again.
disable-the-use-of-the-com-apple-quarantine-extended-attribute-on-mojave
How do I stop the โAre you sure you want to open it?โ dialog box from displaying when I open an app?
how-macos-overrides-app-behaviour-including-quarantine
quarantine-apps
In the past on macOS once you have approved an app that is from an "unidentified developer" the system will keep a record of that exception and stop pestering you with warnings. This doesn't work with the homebrew installed version of FileBot. I am assuming because it's not signed at all? (although other unsigned applications installed with homebrew don't exhibit this behavior)
These are the typical windows we are used to, but allowing this app to run once doesn't resolve the warning for the second launch because it has a quarantine flag set.
To make sure gatekeeper's list of overrides includes my new exception for FileBot.app:
Code: Select all
$ spctl --list | grep -i filebot
2718[UNLABELED] P0 allow execute [/Applications/FileBot.app]
Checking to see if the application is signed shows that it is not signed.
Code: Select all
$ codesign -dvvvv /Applications/FileBot.app
/Applications/FileBot.app: code object is not signed at all
$ codesign --verify -vv /Applications/filebot.app
/Applications/filebot.app: code object is not signed at all
In architecture: x86_64
Code: Select all
xattr -l /Applications/FileBot.app
Code: Select all
sudo xattr -d com.apple.quarantine /Applications/FileBot.app
disable-the-use-of-the-com-apple-quarantine-extended-attribute-on-mojave
How do I stop the โAre you sure you want to open it?โ dialog box from displaying when I open an app?