# Launch separate program for HTTPS prompt 4 messages from 2012-10-23 to 2012-11-13. Participants: 乙酸鋰, Matthieu Moy, Erik Faye-Lund. Thread: https://gitlist.dev/t/31918 ## 乙酸鋰, 2012-10-23 14:39 Subject: Launch separate program for HTTPS prompt Message-ID: URL: https://gitlist.dev/e/CAHtLG6QY-PYUKbNUicox_Ayh70bUSJOL7LGZrQQMqgbVBDmEiA%40mail.gmail.com ``` 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, 2012-10-23 14:48 Subject: Re: Launch separate program for HTTPS prompt Message-ID: URL: https://gitlist.dev/e/vpq6261nt0x.fsf%40grenoble-inp.fr In-Reply-To: ``` 乙酸鋰 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, 2012-11-13 14:51 Subject: Re: Launch separate program for HTTPS prompt Message-ID: URL: https://gitlist.dev/e/CABPQNSYav4K208a1VVP6rK6LhXBo%2Bnkx-DcG4zUsiufnCJkY5g%40mail.gmail.com In-Reply-To: ``` On Tue, Oct 23, 2012 at 4:48 PM, Matthieu Moy wrote: > 乙酸鋰 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, 2012-11-13 15:07 Subject: Re: Launch separate program for HTTPS prompt Message-ID: URL: https://gitlist.dev/e/CABPQNSbpnmhmaCc8kzKn2%2Bc_MACotOx5SxmaRMzPbnW%3DhiP7XA%40mail.gmail.com In-Reply-To: ``` 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, 乙酸鋰 wrote: > 2012/11/13 Erik Faye-Lund : >> On Tue, Oct 23, 2012 at 4:48 PM, Matthieu Moy >> wrote: >>> 乙酸鋰 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. ```