You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically during openssl 1.x to 3.x upgrade, we kept opessl 1.x header+ddl & 3.x ddl in msys2 for older rubies. I'm not sure what was the purpose - I see ri2 bundles the libssl for which it was compiled against in bin/ruby_builtin_dlls. What I found is that the out of box ruby would load the libssl from ruby_builtin_dlls, ignoring the newer DLL in msys2 as the filename simply is different. If I run gem install openssl, now the gem is compiled against new openssl DLL from msys2. I guess the only case it could break is when the user is running gem install openssl requesting an old gem version that won't compile against the new openssl DLL?
@larskanis@MSP-Greg Is there a reason and need to keep two versions of openssl e.g. 3.x header+ddl + 4.x ddl in msys2 just like we had 1.x header+ddl & 3.x ddl in the past?
I already updated all rubyinstaller stable versions (3.3.13, 3.4.12, 4.0.9) to OpenSSL-4. They are all compatible to OpenSSL-4. I didn't finish all testing, but so far there seems to be no API break on the Ruby level by OpenSSL-4, like we had with OpenSSL-1.x and 3.x. The only incompatible change is the removal of engines. But I don't think they are worth to keep OpenSSL-3.
Activity
larskanis commentedon Nov 17, 2026
I already updated all rubyinstaller stable versions (3.3.13, 3.4.12, 4.0.9) to OpenSSL-4. They are all compatible to OpenSSL-4. I didn't finish all testing, but so far there seems to be no API break on the Ruby level by OpenSSL-4, like we had with OpenSSL-1.x and 3.x. The only incompatible change is the removal of engines. But I don't think they are worth to keep OpenSSL-3.
So unless I or someone else finds some incompatible change caused by OpenSSL-4, I don't think there's a need to keep OpenSSL-3. Download of OpenSSL-4 based RI2 versions are here in the artifacts section: https://github.com/oneclick/rubyinstaller2/actions/runs/43856737299
ntkme commentedon Nov 17, 2026
Thank you. I'm going to close this for now.
If anyone discovers any problem with openssl 4 on windows ruby, please comment here and we will reopen this issue and investigate.