-
Notifications
You must be signed in to change notification settings - Fork 588
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
Install.sh doesn't work when adding -k
to curl command due to self-signed cert
#1739
Comments
Same error here. How to address? |
👋 Thanks for filing the issue @thommelutten! - @Natediesel7 - if you're downloading via a proxy or some other configuration you might need to modify this line in the install.sh: Adding There's also the option of downloading the asset directly from the release page: We'll take a look at trying to make the error more transparent or give a workaround for those who need to bypass SSL verification. |
Was this problem ever resolved as I am facing the same issue and don't know how to resolve ?. I cloned the repository and made changes to Install.sh @spiffcs but it still gives me the same error so I am not sure how to proceed with this ?. |
Hi @djbazuka01, sorry for the delay replying, are you still having issues here? Can you share a full capture of the command line you're running, and the output? Thanks. |
The install script always re-downloads itself (to be sure to run the correct installer based on which version is being installed).
to prevent re-download. |
Is this still an issue for anyone? If so, can you help me understand why you would want to pass |
@willmurphyscode It is no longer relevant for me, so it can be closed from my perspective. |
What happend
Running
curl -k -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh | sh -s -- -b /usr/local/bin
when having a self-signed certificate results in the following errorWhat you expected to happen:
Syft would be downloaded and installed.
Anything else we need to know?:
The error is due to the self-signed certificate, and while I don't want to advocate for a
--insecure
flag, the error could be more transparent.The text was updated successfully, but these errors were encountered: