Skip to content

Conversation

@larskanis
Copy link
Member

@larskanis larskanis commented Dec 18, 2025

RubyInstaller-3.4 changed how the builtin libssl library is used. It is only used together with the builtin openssl gem. The buildin openssl gem has it's own CA certificates path.

When a source gem is linked to libssl, then the MSYS2 provided libssl and it's CA certificates are used. Moreover the MSYS2 tools like pacman or curl use a separate file named ca-bundle.crt.

All three diretories are now filled by the c_rehash.rb helper script now. And the README-SSL describes the paths.

RubyInstaller-3.4 changed how the builtin libssl library is used.
It is only used together with the builtin openssl gem.
The buildin openssl gem has it's own CA certificates path.

When a source gem is linked to libssl, then the MSYS2 provided libssl and it's CA certificates are used.
Moreover the MSYS2 tools like pacman or curl use a separate file named `ca-bundle.crt`.

All three diretories are now filled by the `c_rehash.rb` helper script.
And the `README-SSL` describes the paths.
@larskanis larskanis merged commit 2103cec into master Dec 18, 2025
5 of 9 checks passed
@larskanis larskanis deleted the ssl-ca-paths branch December 18, 2025 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants