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

bloodhound 4.1.0 Darwin arm64 release not working #504

Closed
epichoxha opened this issue Feb 10, 2022 · 19 comments
Closed

bloodhound 4.1.0 Darwin arm64 release not working #504

epichoxha opened this issue Feb 10, 2022 · 19 comments
Assignees
Labels

Comments

@epichoxha
Copy link

epichoxha commented Feb 10, 2022

App does not run. Error message:BloodHound.app” is damaged and can’t be opened.

Mac M1

Darwin ****.local 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T8101 arm64
@ddlees ddlees added the bug label Feb 10, 2022
@yellow-starburst
Copy link

Everything breaks with M1 - what do you expect? Lol

@epichoxha
Copy link
Author

:), true. Only golang binaries seem to work flawlessly

@vysecurity
Copy link

+1, but you can compile yourself and it'll work.

@rvazarkar
Copy link
Contributor

@ddlees we'll need to make sure our pipeline uses Node16 going forward I believe

@ddlees ddlees self-assigned this Feb 14, 2022
@ddlees
Copy link
Contributor

ddlees commented Feb 14, 2022

@epichoxha We overhauled our build infrastructure and are now publishing the artifacts from the most recent commit on the master branch to a rolling release. Can you let us know if the arm64 binary that is published there works for you? Thanks!

https://github.com/BloodHoundAD/BloodHound/releases/tag/rolling

@epichoxha
Copy link
Author

@ddlees , nah, still getting the same issue.

“BloodHound.app” is damaged and can’t be opened. You should move it to the Bin.

@vysecurity
Copy link

If you build it, it'll work.

@epichoxha
Copy link
Author

I'll try to build @vysecurity thanks

@andyrobbins
Copy link
Contributor

@epichoxha

I just built the M1 binary on my M1 and verified it works. I went ahead and added it to the release as well: https://github.com/BloodHoundAD/BloodHound/releases/tag/4.1.0

If you'd like to build this yourself, you can clone the repo then run these commands:

npm ci
npm run build

This will create the M1 compatible binary for you

Andy

@epichoxha
Copy link
Author

Hey @andyrobbins thanks. Couldn't find your recent built. I build it myself, it works well.

Thanks

@vysecurity
Copy link

@andyrobbins did you get customqueries.json to work on the ARM build?

@vashirov
Copy link

App is not signed, I had to remove com.apple.quarantine to be able to start it:
xattr -d com.apple.quarantine /Applications/BloodHound.app

@Esonhugh
Copy link

Is the brew one a right M1 Version?

@vashirov
Copy link

Brew only had Intel version. I've submitted a PR to add support for arm64 builds in Homebrew/homebrew-cask#127827

@vashirov
Copy link

What's interesting though is that arm64 version has signing issues while x64 version is just not signed: image
image

@vysecurity
Copy link

issue still exists.

@pwnmeow
Copy link

pwnmeow commented Mar 26, 2024

Its still a issue

@rpetersson
Copy link

When an application gets downloaded from any source other than those that Apple seems suited, the application gets an extended attribute "com.apple.Quarantine". This triggers the message: " is damaged and can't be opened. You should move it to the Bin."
Remove the attribute and you can launch the application.

To do this, open a console and type:

$ xattr -c <path/to/application.app>

Lauch, smile and enjoy.

@benburkhart
Copy link

thanks @rpetersson , worked like a charm

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