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

Multiple GIT Accounts & HTTPS Client Certificates - Config

From
Sergei Haller <sergei@sergei-haller.de>
Date
Sep 10, 2018, 08:09 UTC
Message-ID
<CAPO0KtU=do8nmJggP4-k1BingdseZUuRjWraGjuN01VoEYU=1Q@mail.gmail.com>
Hi folks,

my problem is basically the following: my git server (https) requires authentication using a clent x509 certificate.

And I have multiple x509 certificates that match the server.

when I access the https server using a browser, the browser asks which certificate to use and everything is fine.

When I try to access the git server from the command line (git pull or similar), the git will pick one of the available certificates (randomly or alphabetically) and try to access the server with that client certificate. Ending in the situation that git picks the wrong certificate.

I can workaround by deleting all client certificates from the windows certificate store except the "correct" one => then git command line will pick the correct certificate (the only one available) and everything works as expected.

Workaround is a workaround, I need to use all of the certificates repeatedly for different repos and different other aplications (non-git), so I've been deliting and reinstalling the certificates all the time in the last weeks...

How can I tell git cmd (per config option??) to use a particular client certificate for authenticating to the https server (I could provide fingerprint or serial number or sth like that)

current environment: windows 10 and git version 2.18.0.windows.1

Would be absolutely acceptable if git would ask interactively which client certificate to use (in case its not configurable)

(I asked this question here before: https://stackoverflow.com/questions/51952568/multiple-git-accounts-https-client-certificates-config )

Thanks!
-- 
sergei@sergei-haller.de
.
Next: Randall S. Becker
Message 1 of 5 in “Multiple GIT Accounts & HTTPS Client Certificates - Config”
  1. Sergei HallerSep 10, 2018
  2. Randall S. BeckerSep 10, 2018
  3. Sergei HallerSep 11, 2018
  4. Sergei HallerSep 11, 2018
  5. brian m. carlsonSep 13, 2018

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.