[macOS 14.4.1] “node_exporter” is damaged and can’t be opened. You should move it to the Trash. about node_exporter HOT 10 CLOSED

@gitperr I was able to download via the browser and simply click the button within Privacy & Security. Thus, it's working as expected now and please feel free to close this issue.

from node_exporter.

@gitperr I downloaded it from the releases page on GitHub using Chrome. In any case, I'm seeing the following after I use wget and tar:

./node_exporter --version
[1]    6596 killed     ./node_exporter --version

I believe the codesigning and notarization should be a part of the CI workflow.

from node_exporter.

@conradwt Now the code signed binary is released, please retry downloading and opening node exporter following these steps:

1- get with curl instead of downloading using a browser, make sure it is the correct arch. Here I put arm

curl -L https://github.com/prometheus/node_exporter/releases/download/v1.8.1/node_exporter-1.8.1.darwin-arm64.tar.gz --output node_exporter.tar.gz

2- untar it

tar xvfz node_exporter.tar.gz

3- cd into the untarred directory and run it

cd node_exporter-1.8.1.darwin-arm64 && ./node_exporter

Downloading via a web browser does not work because we are signing with rcodesign instead of Apple's own codesign, until we get Mac build machine, this solution should work.

from node_exporter.

It's a codesigning issue because I was able to use the following to get things working:

codesign -vvv \
  --force \
  --strict \
  --timestamp \
  --options=runtime \
  --sign "Developer ID Application: <NAME> (<TEAMEID>)" ./node_exporter

After you run the executable, one will see the following message:

Then navigate to Settings -> Privacy & Security and click the 'Open Anyway' button towards the bottom of the page.

from node_exporter.

👓 @gitperr

from node_exporter.

You should consider upgrading from v0.16.0. This version is out of date by 6 years.

We also introduced code signing in the latest v1.8.0 release,

from node_exporter.

@SuperQ Yes, the errors that I'm getting are coming from node_exporter v1.8.0. The example output is simply an example of what I expect to see when starting the executable.

from node_exporter.

@SuperQ I think #3008 did not make it into that release you mentioned, we might have forgotten to cut a new release after it was merged.

And just out of curiosity, what was the download method? Even if you download a rcodesign signed binary using Safari directly, it errors out. I try with wget or curl usually, then untar. I was able to make it work like that at least.

from node_exporter.

Code signing was added as SuperQ mentioned, but did not make it to the release you downloaded. Let's try again when a new release is cut including #3008

from node_exporter.

Following the steps in this thread worked - #3008 (comment)

Yes, this codesigned binary needs to be released to make this a seamless process 👍

from node_exporter.