{"thread":{"id":"62846","subject":"[PATCH] docs: indicate http.sslCertType and sslKeyType","startedAt":"2025-01-23T00:16:10Z","lastAt":"2025-02-05T17:46:00Z","messageCount":9,"participants":["Andrew Carter via GitGitGadget","brian m. carlson","Junio C Hamano","Andrew Carter"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"511099","messageId":"pull.1854.git.1737591366672.gitgitgadget@gmail.com","threadId":"62846","inReplyTo":null,"subject":"[PATCH] docs: indicate http.sslCertType and sslKeyType","fromName":"Andrew Carter via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2025-01-23T00:16:06Z","receivedAt":"2025-01-23T00:16:10Z","isPatch":true,"sender":{"key":"andrew@emailcarter.com","avatar":"https://avatars.githubusercontent.com/u/68627532?v=4"},"body":"From: Andrew Carter <andrew@emailcarter.com>\n\nThese useful config options were added in 0a01d41ee4c but lacked\ndocumentation.\n\nSigned-off-by: Andrew Carter <andrew@emailcarter.com>\n---\n    document http.sslCertType and sslKeyType\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-1854%2Fplentydone%2Fcurl-cert-options-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1854/plentydone/curl-cert-options-v1\nPull-Request: https://github.com/gitgitgadget/git/pull/1854\n\n Documentation/config/http.txt | 12 ++++++++++++\n 1 file changed, 12 insertions(+)\n\ndiff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\nindex a14371b5c96..cd39e182527 100644\n--- a/Documentation/config/http.txt\n+++ b/Documentation/config/http.txt\n@@ -216,6 +216,18 @@ http.sslBackend::\n \tThis option is ignored if cURL lacks support for choosing the SSL\n \tbackend at runtime.\n \n+http.sslCertType::\n+\tType of client certificate used when fetching or pushing over HTTPS.\n+\t(e.g. \"PEM\", \"DER\", or \"P12\"). See also libcurl `CURLOPT_SSLCERTTYPE`\n+\tCan be overridden by the `GIT_SSL_CERT_TYPE` environment variable.\n+\n+http.sslKeyType::\n+\tType of client private key used when fetching or pushing over HTTPS.\n+\t(e.g. \"PEM\", \"DER\", or \"ENG\"). Particularly useful when set to \"ENG\"\n+\tfor authenticating with PKCS#11 tokens. See also libcurl\n+\t`CURLOPT_SSLCERTTYPE` . Can be overridden by the `GIT_SSL_KEY_TYPE`\n+\tenvironment variable.\n+\n http.schannelCheckRevoke::\n \tUsed to enforce or disable certificate revocation checks in cURL\n \twhen http.sslBackend is set to \"schannel\". Defaults to `true` if\n\nbase-commit: 4e746b1a31f9f0036032b6f94279cf16fb363203\n-- \ngitgitgadget\n"},{"id":"511100","messageId":"Z5GOfwBR7JBloIs0@tapette.crustytoothpaste.net","threadId":"62846","inReplyTo":"pull.1854.git.1737591366672.gitgitgadget@gmail.com","subject":"Re: [PATCH] docs: indicate http.sslCertType and sslKeyType","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2025-01-23T00:34:07Z","receivedAt":"2025-01-23T00:34:09Z","isPatch":true,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2025-01-23 at 00:16:06, Andrew Carter via GitGitGadget wrote:\n> diff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\n> index a14371b5c96..cd39e182527 100644\n> --- a/Documentation/config/http.txt\n> +++ b/Documentation/config/http.txt\n> @@ -216,6 +216,18 @@ http.sslBackend::\n>  \tThis option is ignored if cURL lacks support for choosing the SSL\n>  \tbackend at runtime.\n>  \n> +http.sslCertType::\n> +\tType of client certificate used when fetching or pushing over HTTPS.\n> +\t(e.g. \"PEM\", \"DER\", or \"P12\"). See also libcurl `CURLOPT_SSLCERTTYPE`\n> +\tCan be overridden by the `GIT_SSL_CERT_TYPE` environment variable.\n> +\n> +http.sslKeyType::\n> +\tType of client private key used when fetching or pushing over HTTPS.\n> +\t(e.g. \"PEM\", \"DER\", or \"ENG\"). Particularly useful when set to \"ENG\"\n> +\tfor authenticating with PKCS#11 tokens. See also libcurl\n> +\t`CURLOPT_SSLCERTTYPE` . Can be overridden by the `GIT_SSL_KEY_TYPE`\n> +\tenvironment variable.\n\nAre there any particular limitations on these values that are platform-\nor backend-specific that we should document?  For instance, I seem to\nrecall that at some point PKCS#12 files were limited to schannel or\nWindows, although I could be mistaken.\n\nDo we also have documentation for whatever engine parameter is required\naccording to the libcurl documentation?\n-- \nbrian m. carlson (they/them or he/him)\nToronto, Ontario, CA\n"},{"id":"511123","messageId":"xmqq7c6ltoib.fsf@gitster.g","threadId":"62846","inReplyTo":"Z5GOfwBR7JBloIs0@tapette.crustytoothpaste.net","subject":"Re: [PATCH] docs: indicate http.sslCertType and sslKeyType","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-01-23T17:43:08Z","receivedAt":"2025-01-23T17:43:11Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"brian m. carlson\" <sandals@crustytoothpaste.net> writes:\n\n> On 2025-01-23 at 00:16:06, Andrew Carter via GitGitGadget wrote:\n>> diff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\n>> index a14371b5c96..cd39e182527 100644\n>> --- a/Documentation/config/http.txt\n>> +++ b/Documentation/config/http.txt\n>> @@ -216,6 +216,18 @@ http.sslBackend::\n>>  \tThis option is ignored if cURL lacks support for choosing the SSL\n>>  \tbackend at runtime.\n>>  \n>> +http.sslCertType::\n>> +\tType of client certificate used when fetching or pushing over HTTPS.\n>> +\t(e.g. \"PEM\", \"DER\", or \"P12\"). See also libcurl `CURLOPT_SSLCERTTYPE`\n>> +\tCan be overridden by the `GIT_SSL_CERT_TYPE` environment variable.\n>> +\n>> +http.sslKeyType::\n>> +\tType of client private key used when fetching or pushing over HTTPS.\n>> +\t(e.g. \"PEM\", \"DER\", or \"ENG\"). Particularly useful when set to \"ENG\"\n>> +\tfor authenticating with PKCS#11 tokens. See also libcurl\n>> +\t`CURLOPT_SSLCERTTYPE` . Can be overridden by the `GIT_SSL_KEY_TYPE`\n>> +\tenvironment variable.\n>\n> Are there any particular limitations on these values that are platform-\n> or backend-specific that we should document?  For instance, I seem to\n> recall that at some point PKCS#12 files were limited to schannel or\n> Windows, although I could be mistaken.\n>\n> Do we also have documentation for whatever engine parameter is required\n> according to the libcurl documentation?\n\nBoth are very good points.\n\nI went back to the original thread that added the change cited in\nthe proposed log message [*1*], hoping that maybe somebody brought\nup caveats but didn't find anything relevant other than that we\npunted to add tests for this since it was too cumbersome to set up.\n\nNote to Andrew, when referring to an existing commit in your\nproposed log message, please do not just write its abbreviated\ncommit object name, like 0a01d41e.\n\nInstead, use it in \"git show -s --format=reference 0a01d41e\" to\nobtain something like\n\n    0a01d41ee4 (http: add support for different sslcert and sslkey\n    types., 2023-03-20)\n\nthat would help people to immediately see what the change was about\nand how old it was.\n\nThanks.\n\n\n[Reference]\n\n*1* https://lore.kernel.org/git/pull.1474.v2.git.git.1679327330032.gitgitgadget@gmail.com/\n"},{"id":"511196","messageId":"f89f8ed0-1d0c-41f4-9360-4fd01b52a517@emailcarter.com","threadId":"62846","inReplyTo":"xmqq7c6ltoib.fsf@gitster.g","subject":"Re: [PATCH] docs: indicate http.sslCertType and sslKeyType","fromName":"Andrew Carter","fromEmail":"andrew@emailcarter.com","sentAt":"2025-01-25T06:38:36Z","receivedAt":"2025-01-25T06:38:40Z","isPatch":true,"sender":{"key":"andrew@emailcarter.com","avatar":"https://avatars.githubusercontent.com/u/68627532?v=4"},"body":"\nOn 1/23/25 11:43 AM, Junio C Hamano wrote:\n> \"brian m. carlson\" <sandals@crustytoothpaste.net> writes:\n>\n>> On 2025-01-23 at 00:16:06, Andrew Carter via GitGitGadget wrote:\n>>> diff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\n>>> index a14371b5c96..cd39e182527 100644\n>>> --- a/Documentation/config/http.txt\n>>> +++ b/Documentation/config/http.txt\n>>> @@ -216,6 +216,18 @@ http.sslBackend::\n>>>   \tThis option is ignored if cURL lacks support for choosing the SSL\n>>>   \tbackend at runtime.\n>>>   \n>>> +http.sslCertType::\n>>> +\tType of client certificate used when fetching or pushing over HTTPS.\n>>> +\t(e.g. \"PEM\", \"DER\", or \"P12\"). See also libcurl `CURLOPT_SSLCERTTYPE`\n>>> +\tCan be overridden by the `GIT_SSL_CERT_TYPE` environment variable.\n>>> +\n>>> +http.sslKeyType::\n>>> +\tType of client private key used when fetching or pushing over HTTPS.\n>>> +\t(e.g. \"PEM\", \"DER\", or \"ENG\"). Particularly useful when set to \"ENG\"\n>>> +\tfor authenticating with PKCS#11 tokens. See also libcurl\n>>> +\t`CURLOPT_SSLCERTTYPE` . Can be overridden by the `GIT_SSL_KEY_TYPE`\n>>> +\tenvironment variable.\n>> Are there any particular limitations on these values that are platform-\n>> or backend-specific that we should document?  For instance, I seem to\n>> recall that at some point PKCS#12 files were limited to schannel or\n>> Windows, although I could be mistaken.\n>>\n>> Do we also have documentation for whatever engine parameter is required\n>> according to the libcurl documentation?\n> Both are very good points.\n>\n> I went back to the original thread that added the change cited in\n> the proposed log message [*1*], hoping that maybe somebody brought\n> up caveats but didn't find anything relevant other than that we\n> punted to add tests for this since it was too cumbersome to set up.\n>\n> Note to Andrew, when referring to an existing commit in your\n> proposed log message, please do not just write its abbreviated\n> commit object name, like 0a01d41e.\n>\n> Instead, use it in \"git show -s --format=reference 0a01d41e\" to\n> obtain something like\n>\n>      0a01d41ee4 (http: add support for different sslcert and sslkey\n>      types., 2023-03-20)\n>\n> that would help people to immediately see what the change was about\n> and how old it was.\n>\n> Thanks.\n>\n>\n> [Reference]\n>\n> *1* https://lore.kernel.org/git/pull.1474.v2.git.git.1679327330032.gitgitgadget@gmail.com/\nThanks for the rapid feedback!\n\nI was leaning away from including too many libcurl-specific details in \nmy original patch, but I see I went too far, and these options are \nmisleading or at least hard to decipher from my initial patch.\n\nAs you mentioned, per the curl documentation [1] the supported values \nare fairly backend-specific.\n\nGit doesn't currently expose the openssl \"engine\" option. Because the \ndefault engine in openssl is \"dynamic\", in my use case, just setting the \nSSLKEYTYPE to \"ENG\" and using a PKCS#11 url in the sslKey field works. I \ncan make a patch to introduce the option if that's desired.\n\nI have something written up that includes backend caveats, and I will \nsubmit another patch this weekend.\n\nThanks for the correction on the commit reference. Please \ncorrect/forgive any list etiquette mistakes.\n\n-AC\n\n1. https://curl.se/libcurl/c/CURLOPT_SSLKEYTYPE.html\n    https://curl.se/libcurl/c/CURLOPT_SSLCERTTYPE.html\n\n"},{"id":"511488","messageId":"dd5d9b93-1585-4165-8f5d-d9737725071e@emailcarter.com","threadId":"62846","inReplyTo":"pull.1854.git.1737591366672.gitgitgadget@gmail.com","subject":"[PATCH v2] docs: indicate http.sslCertType and sslKeyType","fromName":"Andrew Carter","fromEmail":"andrew@emailcarter.com","sentAt":"2025-01-30T13:18:08Z","receivedAt":"2025-01-30T13:19:49Z","isPatch":true,"sender":{"key":"andrew@emailcarter.com","avatar":"https://avatars.githubusercontent.com/u/68627532?v=4"},"body":"\n0a01d41ee4 (http: add support for different sslcert and sslkey types.,\n2023-03-20) added useful SSL config options, but did not document them.\n\nSigned-off-by: Andrew Carter <andrew@emailcarter.com>\n---\n  Documentation/config/http.txt | 15 +++++++++++++++\n  1 file changed, 15 insertions(+)\n\ndiff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\nindex a14371b5c9..38e874307b 100644\n--- a/Documentation/config/http.txt\n+++ b/Documentation/config/http.txt\n@@ -216,6 +216,21 @@ http.sslBackend::\n      This option is ignored if cURL lacks support for choosing the SSL\n      backend at runtime.\n\n+http.sslCertType::\n+    Type of client certificate used when fetching or pushing over HTTPS.\n+    \"PEM\", \"DER\" are supported when using openssl or gnutls backends. \"P12\"\n+    is supported on \"openssl\", \"schannel\", \"securetransport\", and \ngnutls 8.11+.\n+    See also libcurl `CURLOPT_SSLCERTTYPE`. Can be overridden by the\n+    `GIT_SSL_CERT_TYPE` environment variable.\n+\n+http.sslKeyType::\n+    Type of client private key used when fetching or pushing over \nHTTPS. (e.g.\n+    \"PEM\", \"DER\", or \"ENG\"). Only applicable when using \"openssl\" \nbackend. \"DER\"\n+    is not supported with openssl. Particularly useful when set to \n\"ENG\" for\n+    authenticating with PKCS#11 tokens, with a PKCS#11 URL in sslCert \noption.\n+    See also libcurl `CURLOPT_SSLCERTTYPE`. Can be overridden by the\n+    `GIT_SSL_KEY_TYPE` environment variable.\n+\n  http.schannelCheckRevoke::\n      Used to enforce or disable certificate revocation checks in cURL\n      when http.sslBackend is set to \"schannel\". Defaults to `true` if\n-- \n2.39.5 (Apple Git-154)\n"},{"id":"511529","messageId":"xmqqa5b8aqn1.fsf@gitster.g","threadId":"62846","inReplyTo":"dd5d9b93-1585-4165-8f5d-d9737725071e@emailcarter.com","subject":"Re: [PATCH v2] docs: indicate http.sslCertType and sslKeyType","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-01-30T22:22:26Z","receivedAt":"2025-01-30T22:22:28Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andrew Carter <andrew@emailcarter.com> writes:\n\n> 0a01d41ee4 (http: add support for different sslcert and sslkey types.,\n> 2023-03-20) added useful SSL config options, but did not document them.\n>\n> Signed-off-by: Andrew Carter <andrew@emailcarter.com>\n> ---\n>  Documentation/config/http.txt | 15 +++++++++++++++\n>  1 file changed, 15 insertions(+)\n\nwarning: Patch sent with format=flowed; space at the end of lines might be lost.\nerror: corrupt patch at line 10\nhint: Use 'git am --show-current-patch=diff' to see the failed patch\nhint: When you have resolved this problem, run \"git am --continue\".\nhint: If you prefer to skip this patch, run \"git am --skip\" instead.\nhint: To restore the original branch and stop patching, run \"git am --abort\".\nhint: Disable this message with \"git config set advice.mergeConflict false\"\nApplying: docs: indicate http.sslCertType and sslKeyType\nPatch failed at 0001 docs: indicate http.sslCertType and sslKeyType\n\nI thought that the initial iteration I received from you on Jan 23rd\nwas just fine.  Did you change some settings with your MUA?  The patch\nis heavily whitespace damaged, with full of &nbsp;.\n\n\n> diff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\n> index a14371b5c9..38e874307b 100644\n> --- a/Documentation/config/http.txt\n> +++ b/Documentation/config/http.txt\n> @@ -216,6 +216,21 @@ http.sslBackend::\n>      This option is ignored if cURL lacks support for choosing the SSL\n>      backend at runtime.\n>\n> +http.sslCertType::\n> +    Type of client certificate used when fetching or pushing over HTTPS.\n> +    \"PEM\", \"DER\" are supported when using openssl or gnutls backends. \"P12\"\n> +    is supported on \"openssl\", \"schannel\", \"securetransport\", and\n> gnutls 8.11+.\n> +    See also libcurl `CURLOPT_SSLCERTTYPE`. Can be overridden by the\n> +    `GIT_SSL_CERT_TYPE` environment variable.\n> +\n> +http.sslKeyType::\n> +    Type of client private key used when fetching or pushing over\n> HTTPS. (e.g.\n> +    \"PEM\", \"DER\", or \"ENG\"). Only applicable when using \"openssl\"\n> backend. \"DER\"\n> +    is not supported with openssl. Particularly useful when set to\n> \"ENG\" for\n> +    authenticating with PKCS#11 tokens, with a PKCS#11 URL in sslCert\n> option.\n> +    See also libcurl `CURLOPT_SSLCERTTYPE`. Can be overridden by the\n> +    `GIT_SSL_KEY_TYPE` environment variable.\n> +\n>  http.schannelCheckRevoke::\n>      Used to enforce or disable certificate revocation checks in cURL\n>      when http.sslBackend is set to \"schannel\". Defaults to `true` if\n"},{"id":"511849","messageId":"20250205053856.72723-1-andrew@emailcarter.com","threadId":"62846","inReplyTo":"pull.1854.git.1737591366672.gitgitgadget@gmail.com","subject":"[PATCH v2] docs: indicate http.sslCertType and sslKeyType","fromName":"Andrew Carter","fromEmail":"andrew@emailcarter.com","sentAt":"2025-02-05T05:38:56Z","receivedAt":"2025-02-05T05:39:18Z","isPatch":true,"sender":{"key":"andrew@emailcarter.com","avatar":"https://avatars.githubusercontent.com/u/68627532?v=4"},"body":"0a01d41ee4 (http: add support for different sslcert and sslkey types.,\n2023-03-20) added useful SSL config options, but did not document them.\n\nSigned-off-by: Andrew Carter <andrew@emailcarter.com>\n---\n Documentation/config/http.txt | 15 +++++++++++++++\n 1 file changed, 15 insertions(+)\n\ndiff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\nindex a14371b5c9..22a8803dea 100644\n--- a/Documentation/config/http.txt\n+++ b/Documentation/config/http.txt\n@@ -216,6 +216,21 @@ http.sslBackend::\n \tThis option is ignored if cURL lacks support for choosing the SSL\n \tbackend at runtime.\n \n+http.sslCertType::\n+\tType of client certificate used when fetching or pushing over HTTPS.\n+\t\"PEM\", \"DER\" are supported when using openssl or gnutls backends. \"P12\"\n+\tis supported on \"openssl\", \"schannel\", \"securetransport\", and gnutls 8.11+.\n+\tSee also libcurl `CURLOPT_SSLCERTTYPE`. Can be overridden by the\n+\t`GIT_SSL_CERT_TYPE` environment variable.\n+\n+http.sslKeyType::\n+\tType of client private key used when fetching or pushing over HTTPS. (e.g.\n+\t\"PEM\", \"DER\", or \"ENG\"). Only applicable when using \"openssl\" backend. \"DER\"\n+\tis not supported with openssl. Particularly useful when set to \"ENG\" for\n+\tauthenticating with PKCS#11 tokens, with a PKCS#11 URL in sslCert option.\n+\tSee also libcurl `CURLOPT_SSLKEYTYPE`. Can be overridden by the\n+\t`GIT_SSL_KEY_TYPE` environment variable.\n+\n http.schannelCheckRevoke::\n \tUsed to enforce or disable certificate revocation checks in cURL\n \twhen http.sslBackend is set to \"schannel\". Defaults to `true` if\n-- \n2.39.5 (Apple Git-154)\n\n"},{"id":"511850","messageId":"8f9a3a2b-dfa2-4ff4-9f97-e65404315396@emailcarter.com","threadId":"62846","inReplyTo":"xmqqa5b8aqn1.fsf@gitster.g","subject":"Re: [PATCH v2] docs: indicate http.sslCertType and sslKeyType","fromName":"Andrew Carter","fromEmail":"andrew@emailcarter.com","sentAt":"2025-02-05T05:46:21Z","receivedAt":"2025-02-05T05:46:25Z","isPatch":true,"sender":{"key":"andrew@emailcarter.com","avatar":"https://avatars.githubusercontent.com/u/68627532?v=4"},"body":"On 1/30/25 4:22 PM, Junio C Hamano wrote:\n\n> Andrew Carter <andrew@emailcarter.com> writes:\n>\n>> 0a01d41ee4 (http: add support for different sslcert and sslkey types.,\n>> 2023-03-20) added useful SSL config options, but did not document them.\n>>\n>> Signed-off-by: Andrew Carter <andrew@emailcarter.com>\n>> ---\n>>   Documentation/config/http.txt | 15 +++++++++++++++\n>>   1 file changed, 15 insertions(+)\n> warning: Patch sent with format=flowed; space at the end of lines might be lost.\n> error: corrupt patch at line 10\n> hint: Use 'git am --show-current-patch=diff' to see the failed patch\n> hint: When you have resolved this problem, run \"git am --continue\".\n> hint: If you prefer to skip this patch, run \"git am --skip\" instead.\n> hint: To restore the original branch and stop patching, run \"git am --abort\".\n> hint: Disable this message with \"git config set advice.mergeConflict false\"\n> Applying: docs: indicate http.sslCertType and sslKeyType\n> Patch failed at 0001 docs: indicate http.sslCertType and sslKeyType\n>\n> I thought that the initial iteration I received from you on Jan 23rd\n> was just fine.  Did you change some settings with your MUA?  The patch\n> is heavily whitespace damaged, with full of &nbsp;.\n>\n>\n>> diff --git a/Documentation/config/http.txt b/Documentation/config/http.txt\n>> index a14371b5c9..38e874307b 100644\n>> --- a/Documentation/config/http.txt\n>> +++ b/Documentation/config/http.txt\n>> @@ -216,6 +216,21 @@ http.sslBackend::\n>>       This option is ignored if cURL lacks support for choosing the SSL\n>>       backend at runtime.\n>>\n>> +http.sslCertType::\n>> +    Type of client certificate used when fetching or pushing over HTTPS.\n>> +    \"PEM\", \"DER\" are supported when using openssl or gnutls backends. \"P12\"\n>> +    is supported on \"openssl\", \"schannel\", \"securetransport\", and\n>> gnutls 8.11+.\n>> +    See also libcurl `CURLOPT_SSLCERTTYPE`. Can be overridden by the\n>> +    `GIT_SSL_CERT_TYPE` environment variable.\n>> +\n>> +http.sslKeyType::\n>> +    Type of client private key used when fetching or pushing over\n>> HTTPS. (e.g.\n>> +    \"PEM\", \"DER\", or \"ENG\"). Only applicable when using \"openssl\"\n>> backend. \"DER\"\n>> +    is not supported with openssl. Particularly useful when set to\n>> \"ENG\" for\n>> +    authenticating with PKCS#11 tokens, with a PKCS#11 URL in sslCert\n>> option.\n>> +    See also libcurl `CURLOPT_SSLCERTTYPE`. Can be overridden by the\n>> +    `GIT_SSL_KEY_TYPE` environment variable.\n>> +\n>>   http.schannelCheckRevoke::\n>>       Used to enforce or disable certificate revocation checks in cURL\n>>       when http.sslBackend is set to \"schannel\". Defaults to `true` if\n\nSorry for the inconvenience, and thanks for your patience.\n\nThe original message was composed by GitGitGadget. I pasted the v2 patch \ninto Thunderbird initially, which clearly failed.\n\nI sent a new v2 patch using git send-email, and at a glance it looks \nunbroken.\n\nIf further changes are needed I can get an updated patch to you with a \nfaster turnaround now.\n\n-AC\n\n"},{"id":"511894","messageId":"xmqqy0yknv3e.fsf@gitster.g","threadId":"62846","inReplyTo":"8f9a3a2b-dfa2-4ff4-9f97-e65404315396@emailcarter.com","subject":"Re: [PATCH v2] docs: indicate http.sslCertType and sslKeyType","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-02-05T17:45:57Z","receivedAt":"2025-02-05T17:46:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andrew Carter <andrew@emailcarter.com> writes:\n\n> On 1/30/25 4:22 PM, Junio C Hamano wrote:\n>\n>> I thought that the initial iteration I received from you on Jan 23rd\n>> was just fine.  Did you change some settings with your MUA?  The patch\n>> is heavily whitespace damaged, with full of &nbsp;.\n> ...\n> Sorry for the inconvenience, and thanks for your patience.\n>\n> The original message was composed by GitGitGadget. I pasted the v2\n> patch into Thunderbird initially, which clearly failed.\n>\n> I sent a new v2 patch using git send-email, and at a glance it looks\n> unbroken.\n>\n> If further changes are needed I can get an updated patch to you with a\n> faster turnaround now.\n\nThanks for your patience, too.\n\nE-mailed patch workflow is easy for automation, once set-up\ncorrectly, but there is certain entry cost.\n\nQueued.  Let's mark it for 'next'.\n\n"}]}