git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Guymer <scott@scottguymer.co.uk>
To: git@vger.kernel.org
Subject: Potential Bug with Client Certificate Authentication (mTLS)
Date: Wed, 18 Sep 2019 16:42:38 +0200	[thread overview]
Message-ID: <CADvYWYNvBAmr=fSe=CLTr7RLcwXDasffz8B21cBpW6L9UtFLMw@mail.gmail.com> (raw)

I'm trying to pull via HTTPS from a TFS server that has Client
Certificate authentication configured.

I believe I have all the certificates in the right format and simply
using curl with the same certs works but when trying to clone via git
it does not seem to negotiate the client certificate auth and just
gets a 403.

I have scoured the config page to see if there is any info
https://git-scm.com/docs/git-config

Is there any concrete documentation on how to get this working?

I have posted a question on stack overflow that has much more detail
https://stackoverflow.com/questions/57473558/git-with-client-certificates-failing-and-working-with-curl

I'm not sure if this is a bug with GIT or just something i'm not doing
correctly.

Thanks

                 reply	other threads:[~2019-09-18 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADvYWYNvBAmr=fSe=CLTr7RLcwXDasffz8B21cBpW6L9UtFLMw@mail.gmail.com' \
    --to=scott@scottguymer.co.uk \
    --cc=git@vger.kernel.org \
    /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. 
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 NNTP newsgroup(s).