You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dashd, dash-cli, dash-qt, etc should run without any issue other than the normal process of removing the quarantine bit.
Actual behavior
All CLI tools die with SIGKILL.
There are no XProtect or Gatekeeper logs as far as I can tell.
This looks like a toolchain issue (binaries in an incorrect format).
@PastaPastaPasta notes that the binaries are cross-compiled from x64 Linux.
Running codesign -s - ./bin/dash-cli will rewrite the file in such a way that it works, but the issue doesn't appear to be related to the code signing itself since other Go and Rust programs work (signed, self-signed, or unsigned) without issue.
To reproduce
Download and install dashcore, and remove the quarantine bit:
Expected behavior
dashd
,dash-cli
,dash-qt
, etc should run without any issue other than the normal process of removing the quarantine bit.Actual behavior
All CLI tools die with SIGKILL.
There are no XProtect or Gatekeeper logs as far as I can tell.
This looks like a toolchain issue (binaries in an incorrect format).
@PastaPastaPasta notes that the binaries are cross-compiled from x64 Linux.
Running
codesign -s - ./bin/dash-cli
will rewrite the file in such a way that it works, but the issue doesn't appear to be related to the code signing itself since other Go and Rust programs work (signed, self-signed, or unsigned) without issue.To reproduce
dashcore
, and remove the quarantine bit:~/.local/opt/dashcore-20.0.4/bin/dash-cli --help
System information
Tested on
The text was updated successfully, but these errors were encountered: