Loading…
LibreSSL compatibility on Windows #36
+3
−1
2 participants
martinjos
commented
Owner
hsbt
commented
@martinjos Thank you for your patch.
We fixed this issue at https://bugs.ruby-lang.org/projects/ruby-trunk/repository/revisions/52693 on ruby/ruby upstream. Can you test with https://github.com/ruby/ruby/tree/trunk/ext/openssl ?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commits on Nov 15, 2015
This page is out of date. Refresh to see the latest.
Showing
with
3 additions
and 1 deletion.
- +2 −0 ext/openssl/extconf.rb
- +1 −1 ext/openssl/ossl.h
This patch makes the openssl gem compatible with the official release of LibreSSL from the OpenBSD team (https://github.com/libressl-portable/portable) on Windows.
Note: it's actually quite hard to use a particular installed version of the openssl gem. If you just run a script without bundler, it always seems to pick up the built-in version. Meanwhile, if you use bundler, bundler itself seems to load the built-in openssl before starting your program (and in fact, even if the built-in version isn't available, it still somehow seems to load libeay32.dll from OpenSSL). The only way I have found to get the gem and the LibreSSL libraries on their own is to remove or rename the files of the built-in version, and not use bundler.
However, having done this, I have succeeded in using the LibreSSL 2.3.1 Windows x86 binaries (under MinGW) with this gem to download a file using HTTPS (and I've verified that it is only loading the LibreSSL libraries).
See also: issue #37