-
Notifications
You must be signed in to change notification settings - Fork 185
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
cacerts_path may not be enough #1045
Comments
Can you show the full output of the If it's trying to install rebar or hex then the |
Thanks for the environment variable suggestion, I think that was it. I was indeed getting stuck on rebar. And I had been favoring hex.config over the env approach. I'm not yet sure why, but it seems like the macports-based Erlang installation I started with was somehow not right (apart from the OS cert chain not working out-of-the-box). Setting If it's helpful, the dynamics of the environment variable and the For completeness, the full output I was seeing previously is below. Probably nothing more to be done here. Thanks again for the help. Run 1: Erlang + OpenSSL 3.1.6 (from macports)
Run 2: After installing hex from GitHub
Run 3: With HEX_CACERTS_PATH via enironment
Run 4: Erlang + OpenSSL 1.1 (from asdf)
same as run 1 Run 5: Setting HEX_CACERTS_PATH via enironment
Works Run 6: Erlang + OpenSSL 3 (from asdf)
Works |
Hello, I've run into a unusual situation when it comes to SSL certs.
I have an Erlang 27 installation that is unable to run
mix deps.get
because of a bogus expired certificate problem as discussed here. It looks like this:I think there might be an underlying problem on the Erlang side which is an issue for a different repository. Here I wanted to ask about the difference between
cacerts_path
in hex, andcacertfile
in httpc.When
cacerts_path
is set, its contents are sent to:public_key.pem_decode/1
. Could an underlying issue with that call explain why I get a failure from mix, but can get httpc to behave if I configure it directly: like this:That works fine. I think what is happening is Erlang doesn't like my system's default cert chain for whatever reason, but the alternative that hex provides in the form of
cacert_path
is susceptible to the same breakage. Meanwhile,cacertfile
works because it is presumably handled in a different way. But that option is not otherwise available through hex.The alternate cert file I'm passing to httpc happens to be the same as the one shipped with Hex, apart from the timestamp. It also works if I pass in Hex's
ca-bundle.crt
.Version details:
The text was updated successfully, but these errors were encountered: