Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Big Sur "Apple cannot check it for malicious software" #2555

Closed
lcuff opened this issue Mar 4, 2021 · 13 comments
Closed

Big Sur "Apple cannot check it for malicious software" #2555

lcuff opened this issue Mar 4, 2021 · 13 comments
Labels
Milestone

Comments

@lcuff
Copy link

lcuff commented Mar 4, 2021

With Big Sur installed, (version 11.2.1) I downloaded the newest version of Quicksilver (1.6.1). Trying to launch results in the dialog "can't be opened because Apple cannot check it for malicious software". Followed by "This software needs to be updated."
Quciksilver dialog

@skurfer
Copy link
Member

skurfer commented Mar 4, 2021

Code signing broke a couple of years ago. It should be safe to open.

(Right-click it and choose “Open” to allow it to run anyway. You only need to do this once.)

@kconner
Copy link

kconner commented Apr 6, 2021

At least as of macOS 11.2.3, version 1.6.1 as downloaded from qsapp.com won't open even with right-click and Open. The error is no different. What does work is to strip the quarantine metadata entry so Gatekeeper no longer flags it as downloaded code.

xattr -d com.apple.quarantine Quicksilver.app

@kajala
Copy link

kajala commented Apr 19, 2021

xattr -d com.apple.quarantine Quicksilver.app

Got error "App not found" (Launchpad shows Quicksilver.app though)

@finisi
Copy link

finisi commented Apr 20, 2021

Just disable the Gatekeeper to run any unsigned software.
To disable to allow apps from anywhere to be installed use the following command in terminal ::

sudo spctl --master-disable

To re-enable use the following command

sudo spctl --master-enable

@skurfer
Copy link
Member

skurfer commented Apr 20, 2021

Got error "App not found" (Launchpad shows Quicksilver.app though)

@kajala I haven’t tried this, but I Assume you need to cd /Applications first, or specify the whole path in the command: /Applications/Quicksilver.app

@kajala
Copy link

kajala commented Apr 20, 2021

Thanks @skurfer & @finisi the xattr -d com.apple.quarantine /Applications/Quicksilver.app worked!

@radiospiel
Copy link

BTW: Besides CLI shanannigans one can also do the following:

  1. download
  2. doubleclick to start, macOS will complain
  3. Open System Preferences, go to Security & Privacy > General, this should now show a checkbox allowing to run Quicksilver. ("Open Anyway")

@radiospiel
Copy link

This might be a useful addition to the installation guide

@DaveEveritt
Copy link

DaveEveritt commented Jan 11, 2022

This might be a useful addition to the installation guide

I'm on Monterey, obvs same issue.

To head off new issues about signing I updated the actual Quicksilver download page to mention the "ctrl-click -> security dialog; open button" method and sent a pull request. I've done similar for the installation guide repo, also adding a note about installing with Homebrew.

@DaveEveritt
Copy link

DaveEveritt commented Jan 11, 2022

Clarification:

(Right-click it and choose “Open” to allow it to run anyway. You only need to do this once.)

You need to ctrl- or right-click (if you've set that up) the app, choose "open" from the contextual menu, then choose the extra "open" button that now appears in the warning dialog box—only needs doing once. (BTW I'm on Monterey)

@gliptak
Copy link
Contributor

gliptak commented Jan 11, 2022

Dialog/option might not be available in (corporate) more restricted environments.

@DaveEveritt
Copy link

Dialog/option might not be available in (corporate) more restricted environments.

For university/corporate settings etc. I suppose admins would install it. I suppose it's a workaround for those with admin access until the issue is fixed.

@pjrobertson pjrobertson added this to the 1.7.0 milestone Feb 10, 2022
This was referenced Feb 17, 2022
@pjrobertson
Copy link
Member

I'm going to close this issue, and open a new issue at #2654 so we can better keep track of exactly what needs doing.

For those following this issue, you may continue to follow #2654. Our goal is to have this issue fixed for the next version of Quicksilver.

Thanks for all the reports everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants