rjust / defects4j

A Database of Real Faults and an Experimental Infrastructure to Enable Controlled Experiments in Software Engineering Research
MIT License
684 stars 297 forks source link

Fail to run init.sh when buiding docker container #551

Closed ketaiq closed 5 months ago

ketaiq commented 5 months ago

I tried to build a docker container using the provided Dockerfile, but I got following error:

[7/8] RUN ./init.sh:
0.194 Setting up project repositories ...
0.545 curl: (60) SSL certificate problem: unable to get local issuer certificate
0.545 More details here: https://curl.haxx.se/docs/sslcerts.html
0.545
0.545 curl failed to verify the legitimacy of the server and therefore could not 0.545 establish a secure connection to it. To learn more about this situation and 0.545 how to fix it, please visit the web page mentioned above. 0.551 retrying curl https://defects4j.org/downloads/defects4j-repos.zip 0.565 Warning: Illegal date format for -z, --time-cond (and not a file name). 0.565 Warning: Disabling time condition. See curl_getdate(3) for valid date syntax. 0.566 % Total % Received % Xferd Average Speed Time Time Time Current 0.566 Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0.929 curl: (60) SSL certificate problem: unable to get local issuer certificate 0.929 More details here: https://curl.haxx.se/docs/sslcerts.html 0.929 0.929 curl failed to verify the legitimacy of the server and therefore could not 0.929 establish a secure connection to it. To learn more about this situation and 0.929 how to fix it, please visit the web page mentioned above.

PedroTav commented 5 months ago

I'm still having the same issue running the init.sh as well, which is odd because the certificate has been renewed already.

Running openssl s_client -showcerts -connect defects4j.org:443 is giving me the following output: Verification error: unable to verify the first certificate

mernst commented 5 months ago

I believe the issue is now fixed. That is, the curl command now works for me.

@ketaiq Thanks for the bug report; we appreciate it.

@PedroTav It's true that the certificate was renewed, but we forgot to update the chain directives to point to the new intermediate certificate. That is now done.

Please let us know if there are any other problems.