Re: Git GUI vs interactive post-commit hooks

From: Alex Riesen <raa.lkml@gmail.com>
Date: May 22, 2008, 12:53 UTC
Message-ID: <20080522125301.GD3206@steel.home>
In-Reply-To: <20080520230204.GA5383@atjola.homenet>

Björn Steinbrink, Wed, May 21, 2008 01:02:04 +0200:

Show 20 quoted lines

> On 2008.05.21 00:31:58 +0200, Alex Riesen wrote:
> > Bj?rn Steinbrink, Mon, May 19, 2008 15:19:42 +0200:
> > > On 2008.05.19 14:48:14 +0400, Alexander Gladysh wrote:
> > > > 
> > > > Any advice? I do want to input password for my key each time I use it.
> > > 
> > > For a graphical tool, you might want to use something like
> > > gtk-led-askpass, which shows a window with a password prompt. SSH will
> > > make use of it if SSH_ASKPASS contains its path _and_ ssh is not started
> > > from a terminal. Unfortunately, the latter is probably not true for git
> > > gui most of the time.
> > 
> > Redirect stdin from /dev/null
> 
> Does that actually work for you? It didn't work for me, because ssh then
> simply goes and opens /dev/tty to ask for the password.
> 
> $ ssh -V
> OpenSSH_4.7p1 Debian-10, OpenSSL 0.9.8g 19 Oct 2007
>

No :( I took this information from sshs manpage:

     SSH_ASKPASS           If ssh needs a passphrase, it will read the
                           passphrase from the current terminal if it was run
                           from a terminal.  If ssh does not have a terminal
                           associated with it but DISPLAY and SSH_ASKPASS are
                           set, it will execute the program specified by
                           SSH_ASKPASS and open an X11 window to read the
                           passphrase.  This is particularly useful when call‐
                           ing ssh from a .xsession or related script.  (Note
                           that on some machines it may be necessary to redi‐
                           rect the input from /dev/null to make this work.)