Launch separate program for HTTPS prompt

乙酸鋰· Oct 23, 2012, 14:39 UTC · lore

Hi,

Could you launch a separate program for HTTPS prompt like SSH_ASKPASS? This allows GUI programs to answer the trust or not, not via stdin.

Regards, ch3cooli

Matthieu Moy· Oct 23, 2012, 14:48 UTC · re: 乙酸鋰 · lore

Re: Launch separate program for HTTPS prompt

乙酸鋰 <ch3cooli@gmail.com> writes:

> Hi,
>
> Could you launch a separate program for HTTPS prompt like SSH_ASKPASS?
> This allows GUI programs to answer the trust or not, not via stdin.

Read about credential helpers, this is what they are meant for, and they do launch separate programs.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Erik Faye-Lund· Nov 13, 2012, 14:51 UTC · re: Matthieu Moy · lore

Re: Launch separate program for HTTPS prompt

On Tue, Oct 23, 2012 at 4:48 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:

Show 10 quoted lines

> 乙酸鋰 <ch3cooli@gmail.com> writes:
>
>> Hi,
>>
>> Could you launch a separate program for HTTPS prompt like SSH_ASKPASS?
>> This allows GUI programs to answer the trust or not, not via stdin.
>
> Read about credential helpers, this is what they are meant for, and they
> do launch separate programs.
>

The prompting-support for credential helpers didn't survive the inclusion; instead we have git_prompt() that consults GIT_ASKPASS and SSH_ASKPASS or falls back to git_terminal_prompt().

Erik Faye-Lund· Nov 13, 2012, 15:07 UTC · lore

Re: Launch separate program for HTTPS prompt

Please don't cull the CC list or top-post. Other people might be interested, and quoting inline will make it easier to understand what you're replying to in that case. I've restored the CC-list and fixed the quoting for you this time.

On Tue, Nov 13, 2012 at 3:58 PM, 乙酸鋰 <ch3cooli@gmail.com> wrote:

Show 22 quoted lines

> 2012/11/13 Erik Faye-Lund <kusmabite@gmail.com>:
>> On Tue, Oct 23, 2012 at 4:48 PM, Matthieu Moy
>> <Matthieu.Moy@grenoble-inp.fr> wrote:
>>> 乙酸鋰 <ch3cooli@gmail.com> writes:
>>>
>>>> Hi,
>>>>
>>>> Could you launch a separate program for HTTPS prompt like SSH_ASKPASS?
>>>> This allows GUI programs to answer the trust or not, not via stdin.
>>>
>>> Read about credential helpers, this is what they are meant for, and they
>>> do launch separate programs.
>>>
>>
>> The prompting-support for credential helpers didn't survive the
>> inclusion; instead we have git_prompt() that consults GIT_ASKPASS and
>> SSH_ASKPASS or falls back to git_terminal_prompt().
>
> Sorry, I don't understand what you mean.
>
> But I am asking for a solution of for HTTPS prompt which is similar to
> the credential part.

Quote from Documentation/technical/api-credentials.txt:

"Credential helpers are programs executed by git to fetch or save credentials from and to long-term storage (where "long-term" is simply longer than a single git process; e.g., credentials may be stored in-memory for a few minutes, or indefinitely on disk)."

In other words, credential helpers are not intended for prompting the user for a username/password pair. Prompting was included in the first credential-helper proposal, but it didn't survive into the inclusion. But you can override credential queries by setting GIT_ASKPASS or SSH_ASKPASS.

I don't know if the credential-system works or not when using HTTP/HTTPS, it might be that cURL is the one that does the credential-negotiating in that case. But that's not really related to credential-helpers; it affects the whole credential-system.