crc: Can't run crc setup on macOS Catalina - "the developer cannot be verified"

General information

OS: macOS 10.15.1 Catalina
Hypervisor: default
Did you run crc setup before starting it? Yes (but that’s where it fails)

CRC version

N/A - cannot run crc

CRC status

N/A - cannot run crc

CRC config

N/A - cannot run crc

Host Operating System

ProductName:	Mac OS X
ProductVersion:	10.15.1
BuildVersion:	19B88

Steps to reproduce

Download the CRC archive from this page (macOS HyperKit).
Extract the archive.
Move crc into my $PATH (mv ~/Downloads/crc-macos-1.1.0-amd64/crc /usr/local/bin/crc)
Run crc setup

Expected

I would be guided through the CRC setup process.

Actual

After about a minute, I see the following dialog pop up:

It reads:

“crc” cannot be opened because the developer cannot be verified.

macOS cannot verify that this app is free from malware.

Safari downloaded this file today at 9:24 AM

Logs

N/A - crc won’t run

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 2
Comments: 15 (6 by maintainers)

Most upvoted comments

My workaround is to simply remove the quarantine flag, after which crc runs without issues:

sudo xattr -d com.apple.quarantine ~/crc-macos-1.10.0-amd64/crc

I usually create a symlink so that I don’t have to keeping typing in “dot” “slash” (i.e. ./crc):

ln -nsf ~/crc-macos-1.10.0-amd64/crc /usr/local/bin/crc

+10

carlmes on Jun 1, 2020

Workaround is to:

Open the containing folder in Finder (e.g. open /usr/local/bin)
Right-click on crc in Finder.
Click ‘Open’.
Wait for ‘Verifying “crc”’ to fail (this takes about a minute).
You’ll get a popup (see below) asking “Are you sure you want to open it?”
Click ‘Open’ to confirm the security exception.

CRC (the binary—any command) seems to run very slowly under Catalina, though. Could be related to https://github.com/code-ready/crc/issues/727

So, since there’s a workaround, the question is: is it possible for CRC to be signed by a valid developer account (I believe you can get a Developer ID free with any working Apple ID, and use it to sign apps to bypass Gatekeeper) during its build process, so macOS users don’t have to go through these hoops to use it?

geerlingguy on Nov 22, 2019

this is being resolved company wide, but some applications are currently in the process for this. we will hopefully soon

gbraad on May 6, 2020

FYI: Could reproduce with CRC V1.4.0

sebastianfaulhaber on Jan 16, 2020

Here’s how VSCode did it…maybe this helps: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution

I still think that the workaround is not acceptable for many customers. So I kindly ask you to put this up in the list. Thanks a lot.

Regards, Sebastian

sebastianfaulhaber on Mar 27, 2020

@geerlingguy Yes we are working on that, we will prioritise it in next sprint.

praveenkumar on Nov 22, 2019