{"version":"2.1.280","anchor":"openssl-environment-variables-now-passed-through-to-git-subp","canonical_anchor":"openssl-environment-variables-now-passed-through-to-git-subp","heading":"OpenSSL environment variables now passed through to git subprocesses","tier":"notice","area":"Git Integration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/openssl-environment-variables-now-passed-through-to-git-subp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### OpenSSL environment variables now passed through to git subprocesses\n\nOpenSSL environment variables are now passed through to git subprocesses\n\n**What**\n\nWhen Claude Code runs git commands, it now passes through four OpenSSL-related environment variables \u2014 `OPENSSL_CONF`, `OPENSSL_CONF_INCLUDE`, `OPENSSL_MODULES`, and `OPENSSL_ENGINES` \u2014 to the git subprocess, the same way it already handled variables like `DEVELOPER_DIR` and `GIT_TEXTDOMAINDIR`.\n\n**Why**\n\nPreviously these OpenSSL variables were either dropped or split incorrectly when git commands ran, which could break custom OpenSSL configurations (such as those used for enterprise certificate setups). Passing them through as intended lets such configurations work correctly with git operations.\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}