{"version":"2.1.305","anchor":"git-can-be-told-to-use-the-openssl-backend","canonical_anchor":"git-can-be-told-to-use-the-openssl-backend","heading":"Git can be set to use OpenSSL for secure connections","tier":"internal","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/git-can-be-told-to-use-the-openssl-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Git can be set to use OpenSSL for secure connections\n\nA new `opensslBackend` option makes Claude Code pass `http.sslBackend=openssl` to git, aimed at Windows setups\n\n**Unclear.** Nothing says how the `opensslBackend` option is switched on.\n\n**What**\n\nClaude Code can add settings to git when it runs it. A new `opensslBackend` option adds `http.sslBackend=openssl`, which tells git to use OpenSSL for secure (TLS) connections. It sits next to the existing options for Windows' own certificate system, Schannel, so it is aimed at git on Windows.\n\n**Why**\n\nThis could fix problems where git on Windows fails to make secure connections or rejects certificates.\n\n- Area: Windows\n- Names: `opensslBackend`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}