Browse files

docs: explain how to exempt apps from Gatekeeper

  • Loading branch information...
claui committed Sep 3, 2018
1 parent 5afe224 commit e9b85e9bd31d52e9f912f6ec43372f2b12406978
Showing with 18 additions and 0 deletions.
  1. +1 −0
  2. +17 −0 doc/faq/
@@ -55,6 +55,7 @@ If your issue persists, search for it before opening a new one. If you find an o
* [`source is not there` error](doc/reporting_bugs/
* [`wrong number of arguments` error](doc/reporting_bugs/
* [Unlisted reason](doc/reporting_bugs/
* [The app can’t be opened because it is from an unidentified developer](doc/faq/
* [`uninstall` wrongly reports cask as not installed](doc/reporting_bugs/
* [`Error: Unknown command: cask` error](doc/reporting_bugs/
* [My problem isn’t listed](
@@ -0,0 +1,17 @@
# The app can’t be opened because it is from an unidentified developer
Chances are that certain apps will give you a popup message like this:
<img src="" width="532" alt="Gatekeeper message">
This is a [security feature from Apple]( The single most important thing to know is that **you can allow individual apps to be exempt from that feature.** This allows the app to run while the rest of the system remains under protection.
**Always leave system-wide protection enabled,** and disable it only for specific apps as needed.
If you are sure you want to trust the app, you can disable protection for that app by right-clicking its icon and choosing `Open`:
<img src="" width="312" alt="Right-click the app and choose Open">
Finally, click the `Open` button if you want macOS to permanently allow the app to run on this Mac. **Don’t do this unless you’re sure you trust the app.**
<img src="" width="532" alt="Gatekeeper message">

0 comments on commit e9b85e9

Please sign in to comment.