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

SSL warnings during bootstrap #2584

Closed
saleyn opened this issue Jun 24, 2021 · 5 comments
Closed

SSL warnings during bootstrap #2584

saleyn opened this issue Jun 24, 2021 · 5 comments

Comments

@saleyn
Copy link
Contributor

saleyn commented Jun 24, 2021

A bootstrap of a fresh clone under Erlang 24 produces the warnings:

$ ./bootstrap 
./bootstrap:759:18: Warning: http_uri:parse/2 is deprecated and will be removed in OTP 25; use uri_string functions instead
=WARNING REPORT==== 24-Jun-2021::10:02:36.560475 ===
Description: "Authenticity is not established by certificate path validation"
     Reason: "Option {verify, verify_peer} and cacertfile/cacerts is missing"
@ferd
Copy link
Collaborator

ferd commented Jun 24, 2021

Yes, this is expected because we need to go download the certifi app that contains the certificate bundle we use after that. There is no cert bundle to be passed prior to that.

The warning isn't avoidable unless we run options to use the local OS CA bundle, which we should at least add to the CI process but can't easily do in a portable manner without a lot of extra code.

@saleyn
Copy link
Contributor Author

saleyn commented Jun 24, 2021

The first warning though is avoidable by calling uri_string.
Maybe pass the {verify, verify_none} option to avoid the second?

@ferd
Copy link
Collaborator

ferd commented Jun 24, 2021

The uri_string warning is not avoidable because it's using a dynamic call in a try...catch to support many versions.

@saleyn
Copy link
Contributor Author

saleyn commented Jun 25, 2021

The uri_string warning is not avoidable because it's using a dynamic call in a try...catch to support many versions.

I see that it's already properly handled in the version-specific way with the OTP_RELEASE macro in rebar_uri:parse/1. Why wouldn't bootstrap call that function instead, which would effectively eliminate the warning?

@ferd
Copy link
Collaborator

ferd commented Jun 25, 2021

Yeah that should work. I generally avoid that in rebar3 calls because rebar3 might be built on a different version than what runs, but bootstrap is always on an immediate run and should be skippable. I'll make a PR with that and edit this comment with it.

Edit PR: #2585

ferd added a commit to ferd/rebar3 that referenced this issue Jun 25, 2021
bootstrap is always on an immediate run and should be skippable safely
when dealing with compiler versions.

As suggested by @saleyn in erlang#2584
@saleyn saleyn closed this as completed Jun 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants