Bug #13918


Appveyor failure - svn 59961 Use https instead of ftp for libffi downloading

Added by MSP-Greg (Greg L) almost 4 years ago. Updated 11 months ago.

Target version:
ruby -v:
current trunk


See PR 1702.

Builds previous to 2.4 don't have cert files, hence, can't verify.

See Appveyor Ruby & MinGW detail, which has ruby info on 1.9 thru trunk (after package list)...


appveyor.yml.patch (305 Bytes) appveyor.yml.patch MSP-Greg (Greg L), 09/19/2017 03:17 AM

Related issues

Related to Ruby master - Bug #13962: Change to httpsClosedduerst (Martin Dürst)Actions

Updated by usa (Usaku NAKAMURA) almost 4 years ago

  • Assignee set to hsbt (Hiroshi SHIBATA)
  • Status changed from Open to Assigned

Updated by MSP-Greg (Greg L) almost 4 years ago

usa (Usaku NAKAMURA) wrote:

It's not only on 2.4 but also on trunk.

I'm sorry, I wasn't clear. Certs aren't configured correctly on Appveyor for ruby builds previous to 2.4. Hence, a ruby script using them can't verify a https web site. The patch simply changes the ruby version used for building.

Maybe debian has the same problem with cert configuration?

Updated by hsbt (Hiroshi SHIBATA) almost 4 years ago

I added workaround used http at r59964.

I will investigate this later.

Updated by MSP-Greg (Greg L) almost 4 years ago

As you know, without X509::DEFAULT_CERT_FILE or ENV['SSL_CERT_FILE'], properly setup verification won't occur. At present, all Appveyor ruby versions previous to 2.4 have this issue. The above link shows that info.

EDIT: I added an ssl verify test to my Appveyor info run (above link), I also filed an issue with Appveyor.

Thanks again.

Actions #5

Updated by hsbt (Hiroshi SHIBATA) over 3 years ago

  • Related to Bug #13962: Change to https added
Actions #6

Updated by jeremyevans0 (Jeremy Evans) 11 months ago

  • Status changed from Assigned to Closed

Also available in: Atom PDF