git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Alexander Gladysh <agladysh@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org
Subject: Re: Git GUI vs interactive post-commit hooks
Date: Thu, 22 May 2008 14:53:01 +0200	[thread overview]
Message-ID: <20080522125301.GD3206@steel.home> (raw)
In-Reply-To: <20080520230204.GA5383@atjola.homenet>

Björn Steinbrink, Wed, May 21, 2008 01:02:04 +0200:
> 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.)

  parent reply	other threads:[~2008-05-22 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 10:48 Git GUI vs interactive post-commit hooks Alexander Gladysh
2008-05-19 13:19 ` Björn Steinbrink
2008-05-19 13:42   ` Alexander Gladysh
2008-05-19 14:11     ` Björn Steinbrink
2008-05-20 22:31   ` Alex Riesen
2008-05-20 23:02     ` Björn Steinbrink
2008-05-20 23:16       ` Jeff King
2008-05-22 12:53       ` Alex Riesen [this message]
2008-05-22 15:12         ` Björn Steinbrink

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080522125301.GD3206@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=agladysh@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).