Make "rake debug" protective for a Ruby OpenSSL loading error. #783
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to make "rake debug" enhanced, on the way suggested at #780 (comment). I didn't need to take the
rake debug
out fromRakefile
. Because the ruby code is executed in the child process by theruby %Q(-I./lib -ropenssl.so -ve'#{ruby_code}')
in theRakefile
.We experienced a FIPS case specific Ruby OpenSSL error in the loading process of Ruby OpenSSL by calling the
ruby -ropenssl
(require 'openssl'
) built with OpenSSL master branch which includes the commit openssl/openssl@6d47e81 but doesn't include the commit openssl/openssl@3c6e114 fixing the issue.The following error happened at
lib/openssl.rb:22
calling thelib/openssl/ssl.rb
with the OpenSSL commit<14e46600c68ece74970462a60ad20703221747a1> which is between the above 2 commits.
This commit enables the
rake debug
still to print the debugging values in such cases. In this case, therake debug
prints only the base provider without fips provider. That was a bug of OpenSSL.