Re: credential-helpers + remote-helper, starting point?

[Junio C Hamano <gitster@pobox.com>]

Jeff King <peff@peff.net> writes:

> On Thu, May 24, 2012 at 09:20:08PM +0200, Matthieu Moy wrote:
>
>> +------------
>> ++-----+ -----> +-----------------+
>> +| git |  pipe  | git remote-http | --- to HTTP server --->
>> ++-----+ <----- +-----------------+
>> +                    ^      |
>> +                    | pipe |
>> +                    |      v
>> +             +----------------------+
>> +             | git credential-cache |
>> +             +----------------------+
>> +------------
>> +
>> +git remote-http will take care of contacting the HTTP server, do the
>> +actual authentication and see if it's accepted by the server. The
>> +credential helper will deal with the credential store (which can be
>> +done by contacting a keyring daemon) and the prompting if needed.
>
> I feel like adding remote-helpers into the mix just makes the situation
> more complex (and necessitates the diagram).

I would also prefer to see an example _without_ the remote helper, but at
the same time it still helps to have an illustration.

> +This document describes two interfaces: the C API that the credential
> +subsystem provides to the rest of git, and the protocol that git uses to
> +communicate with system-specific "credential helpers". If you are
> +writing git code that wants to look up or prompt for credentials, see

Don't you "prompt" yourself?  The above sounds as if you are delegating
both looking up and prompting to the helper.

> +the section "C API" below. If you want to write your own helper, see
> +the section on "Credential Helpers" below.

Nice.