helm: macOS Catalina error: “helm” cannot be opened because the developer cannot be verified.
Output of helm version: v2.14.3
Information from https://github.com/hashicorp/terraform/issues/23033 suggests that Apple is requiring applications to be signed with an Apple developer key from now on.
A workaround is also mentioned in the above issue and works but it is not ideal.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 21 (8 by maintainers)
as a less dramatic workaround to disabling all protections, you should be able to grant an exception to helm specifically. after you try to open helm and get the error prompt, you can go to System Preferences -> Security & Privacy -> General and it will give you the option to set a special exception for helm:
the next time you try to run helm, you’ll get one last warning prompt that now gives you the option to open helm.
@tdensmore just run
sudo spctl --master-disableref: http://osxdaily.com/2016/09/27/allow-apps-from-anywhere-macos-gatekeeper/I’m using macOS Catalina and helm v2 and v3 CLI work for me there. Under
System Preferences/Security & Privacy/GeneralinAllow apps downloaded from:I have set toAnywhereThanks @rimus .
sudo spctl --master-disableworks for me.You can run
xattr -d com.apple.quarantine /path/to/fileto whitelist the binary from CLI. As others have noted, disabling gatekeeper usingspctlshould be avoided.@rimusz I do not have that option. My only options are:
App StoreandApp Store and identified developersI worked around this by deleting helm and then downloading it with wget.
It seems that it is because the file was downloaded via chrome. I’m guessing you also have this problem if helm has been downloaded via safari or firefox.
Allow apps from anywhere and
sudo spctl --master-disabledisable protections that can potentially leave a Mac vulnerable to malware, and should be avoided if at all possible. This is not an ideal solution.After taking the following steps, I now seem to have an “Open anyways” option now, allowing running individual applications without disabling secure defaults.
Here’s what I did, not sure if all steps are relevant:
spctloff and on:Found the solution
Do not download the archive with a GUI browser, it will get tainted by macos that will pretend downloaded binaries to be signed.
Just download with wget or curl, and live happy!
Downloaded archives/binaries get some additional attributes on the file system, look at a
ls -lof your Downloads folderYou see the
@sign right after the permissions? that is the extended attribute, and files downloaded by curl will not have itWow, @micheas is right! If I download RC3 with
wgetit works but with chrome it triggers MacOS’s security (Gatekeeper).Googling a bit led me to this info: “Additionally, Gatekeeper only monitors files downloaded from the Internet through an Internet browser…”
This is good news as it means installing helm using
brewwill not trigger the security prompt. I have confirmed this.This explains why it worked for my installation of
kubectl.