-
Notifications
You must be signed in to change notification settings - Fork 83
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
ACVM displays malware issue on launch (M1 MBA 2020) #40
Comments
Can also confirm this issue happens with Big Sur 11.4, also on an M1 MBA, so it isn't just a Monterey issue. Even building 1.0-4 from source, it still won't let you start the VM (even though it lets you open the app). |
got same here bigsure m1 |
Apple revoked the signing certificate so the pre-built binary is no longer valid. If you need this, you can try to build and run with Xcode. |
I was able to get the downloadable binary available from this repo (the Dec. 2020 file) working, didn't have to build it myself. You may only need to do steps 1, 6, and 7, not sure. I was throwing every, "Yes ok I get it please just let it work," thing I could find at it. Steps 6/7 are likely all that's needed for people who build it from source and still have issues.
Create a plain text file on your desktop and paste this in. Make sure it's plain text.
|
I can confirm that this method really solves the issue! |
When I double click on the ACVM app, an error pops up that displays the following:
"ACVM vill damage your computer. You should move it to the Bin". It also displays "You do not have permission to open the application ACVM. Contact your computer or network administrator for assistance." In this case, my computer is running macOS Monterey Beta 3, so the issue may be related to that. I downloaded ACVM v1.0-3, as it is the latest version that had an ACVM.zip file instead of the source code. I am trying to run either ParrotOS or Kali Linux with ACVM and any help would be greatly appreciated. Attached are screenshots of the errors.
The text was updated successfully, but these errors were encountered: