From: Junio C Hamano <junkio@cox.net>
Date: Mon, 26 Sep 2005 20:43:39 GMT
Subject: Re: [PATCH 1/3] Support for SSL client cert
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.