git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] http: add support for different sslcert and sslkey types.

From
Jeff King <peff@peff.net>
Date
Mar 21, 2023, 17:22 UTC
Message-ID
<20230321172245.GB3119834@coredump.intra.peff.net>
In-Reply-To
<CAEpdKf=THU=sc3S3W4azBmYp7+J945GxFqhh_i-5kV0kunMdNw@mail.gmail.com>
On Mon, Mar 20, 2023 at 09:21:44PM +0300, Stanislav M wrote:
Show 20 quoted lines
> > > @@ -1014,10 +1020,14 @@ static CURL *get_curl_handle(void)
> > >
> > >       if (ssl_cert)
> > >               curl_easy_setopt(result, CURLOPT_SSLCERT, ssl_cert);
> > > +     if (ssl_cert_type)
> > > +             curl_easy_setopt(result, CURLOPT_SSLCERTTYPE, ssl_cert_type);
> >
> > We're just feeding curl whatever string the user gave us (which is good,
> > since we don't know which ones are valid). But what happens with:
> >
> >   GIT_SSL_CERT_TYPE=bogus git fetch ...
> >
> > Should we check for an error here, or will the actual request later
> > complain properly?
> 
> Curl itself validates that string. And if we pass the wrong type or
> not pass 'ENG' in case of pkcs11: curl will return an error. In that
> case git do the same if GIT_SSL_CERT passed wrong ss 'ENG' in case of
> pkcs11: curl will return an error. In that case git do the same if
> GIT_SSL_CERT passed wrong
That sounds great. Thanks for confirming!
-Peff
Previous: Stanislav MNext: Junio C Hamano
Message 5 of 16 in “That change for support different sslcert and sslkey types.”
  1. That change for support different sslcert and sslkey types.Stanislav Malishevskiy via GitGitGadget, Mar 19, 2023
  2. http: add support for different sslcert and sslkey types.Stanislav Malishevskiy via GitGitGadget, Mar 20, 2023
  3. Jeff KingMar 20, 2023
  4. Stanislav MMar 20, 2023
  5. Jeff KingMar 21, 2023
  6. Junio C HamanoMar 20, 2023
  7. Stanislav MMar 20, 2023
  8. Jeff KingMar 21, 2023
  9. Junio C HamanoMar 21, 2023
  10. Stanislav MMar 23, 2023
  11. Jeff KingMar 23, 2023
  12. Stanislav MMar 23, 2023
  13. Junio C HamanoMar 29, 2023
  14. Stanislav MMar 29, 2023
  15. Jeff KingMar 29, 2023
  16. Junio C HamanoMar 30, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.