I am upgrading our ruby to the latest version in the toolbox, from 3.3.7 to 3.4.4. 

We have some ruby gems installed that use "digest/sha1" (even on the latest available gem version):

require 'digest/sha1'

On the older ruby version 3.3.7 from the toolbox this works (and the gems that use this also work)

# ruby -v
ruby 3.3.7 (2025-01-15 revision be31f993d7) [powerpc-aix7.1.0.0]
# ruby
require 'digest/sha1'
#

However when upgraded to the latest ruby 3.4.4 version from the toolbox this no longer works. 

# ruby -v
ruby 3.4.4 (2025-05-14 revision a38531fd3f) +PRISM [powerpc-aix7.1.0.0]
# ruby
require 'digest/sha1'
<internal:/opt/freeware/share/ruby/3.4/rubygems/core_ext/kernel_require.rb>:136:in 'Kernel#require': rb_digest_wrap_metadata not found (LoadError)
        from <internal:/opt/freeware/share/ruby/3.4/rubygems/core_ext/kernel_require.rb>:136:in 'Kernel#require'
        from -:1:in '<main>'
#

It probably is not ideal to be using digest/sha1, but it is what the gems we are using require, and it should work? I don't believe the function is deprecated in ruby? 

Any help appreciated - we can't upgrade to this ruby version right now as the gems we need to install do not work with it.  

Thanks,

Alan

can you tell me what the output is?  dump -H /path/to/digest.so ? 

might be a build issue, whats the output for: dump -H /path/to/digest.so ?

Hi Aaron,

Thanks for the response. 

Here is the 32bit and 64bit output (the gems we are running require the 32bit version of ruby, but the errors happen with both 32 and 64bit):

Regards,

Alan

Any feedback from the IBM team who built the ruby 3.4.4 version whether this change in behaviour is expected on the new version, or if there is a build/packaging issue here?

Hi Alan,

Thank you for bringing this to our attention. We have successfully reproduced the issue on our system, and we are currently working on identifying and resolving it.

sha1 use is deprecated - from 2022 NIST Retires SHA-1 Cryptographic Algorithm

Agreed. However ruby has not deprecated support for SHA1 (as far as I am aware), so it should still work. 

Yes, but if every time something is deprecated you remove support from tooling, you're forcing everybody to stop updating/upgrading/improving.

I've seen way too many machines stuck in the past (e.g. 1990's) due to removal of algorithms from the code, those machines could still be current if the code was there, just disabled by default.