Bug #13918: Appveyor failure - svn 59961 Use https instead of ftp for libffi downloading

• Status: Closed
• Assignee: hsbt (Hiroshi SHIBATA)
• Target version: -
• ruby -v: current trunk
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
• Tags: win, build

[MSP-Greg (Greg L)]

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)...

[usa (Usaku NAKAMURA)]

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

It's not only on 2.4 but also on trunk.
See https://rubyci.org/logs/www.rubyist.net/~akr/chkbuild/debian/ruby-trunk/log/20170919T024800Z.fail.html.gz

[MSP-Greg (Greg L)]

usa (Usaku NAKAMURA) wrote:

It's not only on 2.4 but also on trunk.
See https://rubyci.org/logs/www.rubyist.net/~akr/chkbuild/debian/ruby-trunk/log/20170919T024800Z.fail.html.gz

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?

[hsbt (Hiroshi SHIBATA)]

I added workaround used http at r59964.

I will investigate this later.

[MSP-Greg (Greg L)]

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.

[hsbt (Hiroshi SHIBATA)]

• Related to Bug #13962: Change http://unicode.org to https added

[jeremyevans0 (Jeremy Evans)]

• Status changed from Assigned to Closed