git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>, Nick Hengeveld <nickh@reactrix.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] Support for SSL client cert
Date: Mon, 26 Sep 2005 13:43:39 -0700	[thread overview]
Message-ID: <7v3bnrh85g.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050926182341.GA26340@pasky.or.cz> (Petr Baudis's message of "Mon, 26 Sep 2005 20:23:41 +0200")

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.

  parent reply	other threads:[~2005-09-26 20:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 17:51 [PATCH 1/3] Support for SSL client cert Nick Hengeveld
2005-09-26 18:23 ` Petr Baudis
2005-09-26 18:36   ` Nick Hengeveld
2005-09-26 20:43   ` Junio C Hamano [this message]
2005-09-27  0:15     ` Nick Hengeveld
2005-09-27  0:43       ` More Porcelains? Junio C Hamano
2005-09-27  0:57         ` Ameer Armaly
2005-09-27  6:15         ` Daniel Barkalow
2005-09-27  8:16         ` Catalin Marinas
2005-09-27 17:02           ` Mariano Videla
2005-09-28 11:30         ` Vincent Hanquez
2005-09-28 20:22         ` Matthias Urlichs

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=7v3bnrh85g.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=nickh@reactrix.com \
    --cc=pasky@suse.cz \
    /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).