Re: Credential helpers processing order

From: Jacob Keller <jacob.keller@gmail.com>
Date: Aug 16, 2016, 15:58 UTC
Message-ID: <CA+P7+xpe2FeBjO0AEHTyuZPEOpCUmt=vUcs5RFYhE9KTZWLNhw@mail.gmail.com>
In-Reply-To: <CAC+L6n0j0=6haBprM2ip75=orEi_5oBedHV1iPBTgi-N8Y6=4A@mail.gmail.com>

On Tue, Aug 16, 2016 at 8:13 AM, Dmitry Neverov <dmitry.neverov@gmail.com> wrote:

Show 12 quoted lines

> Hi,
>
> I wonder why credential helpers are called in the order: system,
> global, local, command-line and not in the reverse order? This make it
> impossible to provide a custom helper and disable default ones via
> command-line parameter. My use-case is to clone a repository in a
> non-interactive environment where a system-level GUI helper is
> configured: clone hangs since system-level helper called first and
> there is no input from the user. Also if a system-level helper sets
> quit=true, then lower-level helpers won't be called at all. Is it by
> design?
>

If I understand correctly, the credential helpers aren't supposed to require input so it is assumed they can be tried in sequence if one fails? It might make sense to reverse the order though...

Thanks, Jake

Show 6 quoted lines

> --
> Dmitry
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html