Updated OpenSSL to version 3.2.2. Extension developers using any functionality relying on OpenSSL should test that their extensions function as expected.
Also, (although not critical) it is not necessary to use the API Sketchup::require method to load Ruby standard library files. It will just add another call to the call stack as the API method will just pass the argument on to the global require method.
I just tested loading OpenSSL on the latest version of SU 2024 and got a true result.
Something odd is going on. All versions of SU should be able to load OpenSSL.
Or, all versions will load the dlls they were compiled with (they’re bundled with the SU install). Older versions do use OpenSSL 1.1 or 1.0, which are EOL.
EDIT:
You might have the user check if the files needed exist. The error text you listed shows there is an issue loading openssl.so (from openssl.rb:13).
For SU 2024.0.2 (24.0.594), the dll files libcrypto-3-x64.dll & libssl-3-x64.dll should exist.
For SU 2024.0.1 (24.0.553) and earlier, the dll files libcrypto-1_1-x64.dll & libssl-1_1-x64.dll should exist. Also, at some point, the dll’s also existed in the SU root folder. Not sure what version changed that…
I’d appreciate that. I’ve watched the ruby/openssl repo on GitHub for a long time, and have also worked with OpenSSL, both Ruby and C. I have one extension, and the last update (early 2024) added a feature to check for updates, as they host it on their own web site. The code uses OpenSSL.
Between the extension and my GitHub activity, I don’t recall the problem your user is having occurring on Windows. There have been some macOS issues (stand-alone Ruby, not with SU), but that was related to some Ruby version managers installing/changing the default cert data.
Maybe anti-virus not liking the compiled *.so file, not sure…