Re: GIT/SSH_ASKPASS used for username input in https:// URLs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 06, 2019 at 03:47:18PM +0200, Andreas Krey wrote:

> there is an interesting wart around prompt.c -
> PROMPT_ECHO isn't used in invoking an external helper program.
> 
> Thus, if I clone something on https (which requires auth for that),
> and have SSH_ASKPASS set, I will get two GUI *password* prompts,
> even though the first one will indicate in the title that it *is*
> asking for the username.
> 
> But basically, given the trivial protocol of SSH_ASKPASS, there
> doesn't seem to be any way to properly fix this without support
> from any desktop environment that sets SSH_ASKPASS. :-(

Yep. If you haven't seen it, there's more discussion in this recent
thread:

  https://public-inbox.org/git/20190429234028.GA24069@xxxxxxxxxxxxxxxxxxxxx/

> The best I can currently tell my users is to use the
>    [credentials "https:/..."]
> configuration to fix the username.

Yes, that works. Or a credential helper could prompt with a better
interface (but AFAIK, the only one written that does so is the Windows
one).

> But if we can't fix this, maybe we can at least point this out in the
> docs?

Sounds like a good suggestion. Where would you look for it? In the
description of GIT_ASKPASS / core.askpass?

-Peff



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux