CI: List OpenSSL providers by openssl CLI in FIPS cases.

[junaruga]

This PR is to add the step to list OpenSSL providers in FIPS cases.
While we are calling the logic to list the OpenSSL providers in the rake test or rake test_fips. In the case where the fips provider is not loaded, the Ruby OpenSSL aborts before printing the providers. This PR enables the CI to print the providers such cases.

I was able to find the fips provider was not loaded with the openssl-head fips case by this commit.
https://github.com/junaruga/ruby-openssl/actions/runs/10078885746/job/27864878836#step:7:1

Below is the commit message.

---

Add the step to list OpenSSL providers available on OpenSSL 3.0 or later versions to check if the base and fips providers are loaded in the FIPS cases.

We have a logic to print the OpenSSL providers in the Rake test and test_fips tasks calling the debug task.

openssl/Rakefile

Line 72 in 16aa2b2

Providers: #{providers_str}

However, if the fips provider is not loaded, the Ruby OpenSSL aborts before printing the OpenSSL providers in the Rake debug task. https://github.com/ruby/openssl/actions/runs/10077703798/job/27860837398#step:13:35

This commit enables CI to print the loaded OpenSSL providers in such case.

Added the '-Wl,-rpath,$(LIBRPATH)' to call the openssl cli without setting LD_LIBRARY_PATH.
See https://github.com/ruby/openssl/blob/master/CONTRIBUTING.md#with-different-versions-of-openssl for details.

[rhenium]

This seems redundant. We print the loaded providers in the Rake task "debug", which is run as part of rake test or rake test_fips.

[junaruga]

This seems redundant. We print the loaded providers in the Rake task "debug", which is run as part of rake test or rake test_fips.

I am mentioning your point at my first comment. Yes, it is redundant. However, my point for this PR is about if we want to list the providers in the case the rake debug fails to print the providers for some error. The case is what we experienced recently.

[rhenium]

However, if the fips provider is not loaded, the Ruby OpenSSL aborts before printing the OpenSSL providers in the Rake debug task. https://github.com/ruby/openssl/actions/runs/10077703798/job/27860837398#step:13:35

I overlooked this part. Perhaps we want to extract the "debug" task out of Rakefile, and print these constants with only openssl.so loaded?

I don't think having duplicate output in every CI run just in case OpenSSL breaks in a similar way will be useful (which mostly likely require a bugfix in openssl/openssl, not in ruby/openssl).

[junaruga]

However, if the fips provider is not loaded, the Ruby OpenSSL aborts before printing the OpenSSL providers in the Rake debug task. https://github.com/ruby/openssl/actions/runs/10077703798/job/27860837398#step:13:35

I overlooked this part. Perhaps we want to extract the "debug" task out of Rakefile, and print these constants with only openssl.so loaded?

I tested your approach with only openssl.so loaded. And it works in the case where Ruby OpenSSL's initial process raises an error by require 'openssl'. I am going to send another PR with the way.

I don't think having duplicate output in every CI run just in case OpenSSL breaks in a similar way will be useful (which mostly likely require a bugfix in openssl/openssl, not in ruby/openssl).

Yes, I would agree with your option.

[junaruga]

However, if the fips provider is not loaded, the Ruby OpenSSL aborts before printing the OpenSSL providers in the Rake debug task. https://github.com/ruby/openssl/actions/runs/10077703798/job/27860837398#step:13:35

I overlooked this part. Perhaps we want to extract the "debug" task out of Rakefile, and print these constants with only openssl.so loaded?

I tested your approach with only openssl.so loaded. And it works in the case where Ruby OpenSSL's initial process raises an error by require 'openssl'. I am going to send another PR with the way.

I sent the PR #783.