From: Jeff King <peff@peff.net>
To: Stanislav M <stanislav.malishevskiy@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Stanislav Malishevskiy via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Stanislav Malishevskiy <s.malishevskiy@auriga.com>
Subject: Re: [PATCH v2] http: add support for different sslcert and sslkey types.
Date: Thu, 23 Mar 2023 14:01:59 -0400 [thread overview]
Message-ID: <20230323180159.GA1015351@coredump.intra.peff.net> (raw)
In-Reply-To: <CAEpdKf=pMcMn6q0wGGcrFN1yi1duguSNLDkqhDmvMBeKQ--yuA@mail.gmail.com>
On Thu, Mar 23, 2023 at 12:33:59PM +0300, Stanislav M wrote:
> I want to do some clarification there. Those changes are not related
> to http or https directly.
> That only configures curl to know how to access the certificate and
> key locally on the client box, so if the way is wrong there is a
> simple error: Certificate or key not found.
Yes, but I'm not sure if there is a way for Git to trigger curl to look
at the certificate that does not involve feeding it an https URL (and we
want a valid one, because we want to see that it correctly speaks to the
server).
-Peff
next prev parent reply other threads:[~2023-03-23 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 13:51 [PATCH] That change for support different sslcert and sslkey types Stanislav Malishevskiy via GitGitGadget
2023-03-20 15:48 ` [PATCH v2] http: add support for " Stanislav Malishevskiy via GitGitGadget
2023-03-20 17:10 ` Jeff King
2023-03-20 18:21 ` Stanislav M
2023-03-21 17:22 ` Jeff King
2023-03-20 17:23 ` Junio C Hamano
2023-03-20 18:24 ` Stanislav M
2023-03-21 17:22 ` Jeff King
2023-03-21 17:43 ` Junio C Hamano
2023-03-23 9:33 ` Stanislav M
2023-03-23 18:01 ` Jeff King [this message]
2023-03-23 18:16 ` Stanislav M
2023-03-29 18:53 ` Junio C Hamano
2023-03-29 19:22 ` Stanislav M
2023-03-29 23:23 ` Jeff King
2023-03-30 0:20 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230323180159.GA1015351@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=s.malishevskiy@auriga.com \
--cc=stanislav.malishevskiy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).