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

Re: [PATCH 1/3] Support for SSL client cert

From
Junio C Hamano <junkio@cox.net>
Date
Sep 26, 2005, 20:43 UTC
Message-ID
<7v3bnrh85g.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20050926182341.GA26340@pasky.or.cz>
Petr Baudis <pasky@suse.cz> writes:
> Could we please have at least --sslkey, if not having 'ssl' prepended to
> all of them? You never know when you'll want to call something else like
> that in the future... ;-)
That is a valid concern.

Anoter possibility is to read them from the environment, since we already do SSL_NO_VERIFY from there.

If we go that route, it might make sense to have something like the following in .git/remotes/that-site file:

    URL: https://some.company.site.xz
    ENV: GIT_SSL_KEY='/home/user/.ssl/'My ssl key'
    ENV: GIT_SSL_CERT='/home/user/.ssl/certs/My Certificate'
    ENV: GIT_SSL_CAPATH='/home/user/.ssl/My CA'
    ...

then at the beginning of git-fetch, we could eval these ENV lines.

Previous: Nick HengeveldNext: Nick Hengeveld
Message 4 of 12 in “Support for SSL client cert”
  1. 1/3 Support for SSL client certNick Hengeveld, Sep 26, 2005
  2. Petr BaudisSep 26, 2005
  3. Nick HengeveldSep 26, 2005
  4. Junio C HamanoSep 26, 2005
  5. Nick HengeveldSep 27, 2005
  6. More Porcelains?Junio C Hamano, Sep 27, 2005
  7. Ameer ArmalySep 27, 2005
  8. Daniel BarkalowSep 27, 2005
  9. Catalin MarinasSep 27, 2005
  10. Mariano VidelaSep 27, 2005
  11. Vincent HanquezSep 28, 2005
  12. Matthias UrlichsSep 28, 2005

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.