{"thread":{"id":"36630","subject":"Git abuses qt4-ssh-askpass","startedAt":"2014-05-10T08:41:28Z","lastAt":"2014-05-12T20:46:42Z","messageCount":3,"participants":["Chris “Kwpolska” Warrick","Felipe Contreras","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"241240","messageId":"CAMw+j7L1YkwjYZibOpuJDnC3FjaRZgBCKBMQcUyT9uRis3heFQ@mail.gmail.com","threadId":"36630","inReplyTo":null,"subject":"Git abuses qt4-ssh-askpass","fromName":"Chris “Kwpolska” Warrick","fromEmail":"kwpolska@gmail.com","sentAt":"2014-05-10T08:41:28Z","receivedAt":"2014-05-10T08:41:28Z","isPatch":false,"sender":{"key":"kwpolska@gmail.com","avatar":null},"body":"Hello,\n\nwhen I’m using the HTTPS protocol to access repositories, a window\nfrom /usr/bin/qt4-ssh-askpass comes up.  It asks for my “SSH pass\nphrase”, twice.  Sadly, it’s wrong.  The actual things it wants is the\nusername in the first case, and the password used to access the remote\nrepository (eg. my GitHub password) in the second question.  This is a\nbug, and very misleading behavior.\n\n-- \nChris “Kwpolska” Warrick <http://kwpolska.tk>\nPGP: 5EAAEA16\nstop html mail | always bottom-post | only UTF-8 makes sense\n"},{"id":"241242","messageId":"536de9584815a_239010732fc43@nysa.notmuch","threadId":"36630","inReplyTo":"CAMw+j7L1YkwjYZibOpuJDnC3FjaRZgBCKBMQcUyT9uRis3heFQ@mail.gmail.com","subject":"RE: Git abuses qt4-ssh-askpass","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2014-05-10T08:54:48Z","receivedAt":"2014-05-10T08:54:48Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Chris “Kwpolska” Warrick wrote:\n> when I’m using the HTTPS protocol to access repositories, a window\n> from /usr/bin/qt4-ssh-askpass comes up.  It asks for my “SSH pass\n> phrase”, twice.  Sadly, it’s wrong.  The actual things it wants is the\n> username in the first case, and the password used to access the remote\n> repository (eg. my GitHub password) in the second question.  This is a\n> bug, and very misleading behavior.\n\nSame in seahorse (two password prompts).\n\n-- \nFelipe Contreras"},{"id":"241317","messageId":"20140512204642.GC2329@sigill.intra.peff.net","threadId":"36630","inReplyTo":"CAMw+j7L1YkwjYZibOpuJDnC3FjaRZgBCKBMQcUyT9uRis3heFQ@mail.gmail.com","subject":"Re: Git abuses qt4-ssh-askpass","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2014-05-12T20:46:42Z","receivedAt":"2014-05-12T20:46:42Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, May 10, 2014 at 10:41:28AM +0200, Chris “Kwpolska” Warrick wrote:\n\n> when I’m using the HTTPS protocol to access repositories, a window\n> from /usr/bin/qt4-ssh-askpass comes up.  It asks for my “SSH pass\n> phrase”, twice.  Sadly, it’s wrong.  The actual things it wants is the\n> username in the first case, and the password used to access the remote\n> repository (eg. my GitHub password) in the second question.  This is a\n> bug, and very misleading behavior.\n\nIf you have GIT_ASKPASS or SSH_ASKPASS set and git needs to prompt for a\nusername or password, it will call that program rather than prompting on\nthe terminal. It does pass a meaningful label to the askpass program,\nbut it sounds like your askpass program does not actually display it.\n\nE.g., try setting GIT_TRACE=1. I get:\n\n  $ GIT_TRACE=1 SSH_ASKPASS=ssh-askpass-fullscreen git fetch\n  trace: built-in: git 'fetch'\n  trace: run_command: 'git-remote-https' 'origin' 'https://github.com/peff/test'\n  trace: run_command: 'ssh-askpass-fullscreen' 'Username for '\\''https://github.com'\\'': '\n  trace: run_command: 'ssh-askpass-fullscreen' 'Password for '\\''https://peff@github.com'\\'': '\n\nand the askpass program shows me those prompts. You may want to file a\nbug report with qt4-ssh-askpass, as most other askpass programs\n(including the original ssh-askpass that comes with ssh) respects the\nprompt arguments.\n\nThat being said, we may be able to improve git, depending on what you\nactually wanted to happen. For example, I don't think there is a way to\ntell git \"even though I have SSH_ASKPASS set, still prompt me on the\nterminal\". It's been generally assumed that you would only set that\nvariable if you preferred an external prompt to a terminal prompt.\n\nYou may also want to look into git's credential support (see \"git help\ncredential\"), which can let you store the username and password in\nsecure system-provided storage (however from the qt4 above, I guess you\nmight be using KDE, and I do not know of a KDE Wallet helper; there is\none for GNOME keyring).\n\n-Peff\n"}]}