git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Paul <lists@pote.com>, git@vger.kernel.org
Subject: Re: why multiple password prompts?
Date: Sat, 29 Mar 2008 09:59:04 -0700 (PDT)	[thread overview]
Message-ID: <m37iflv54l.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LNX.1.00.0803291241020.19665@iabervon.org>

Daniel Barkalow <barkalow@iabervon.org> writes:

> On Sat, 29 Mar 2008, Paul wrote:

Paul who?

>> When I do a simple git-pull over SSH, why does it typically prompt
>> me for my SSH password two or three times? And no, I am not
>> inputting it wrong.
> 
> In some versions of git, it makes separate connections to find out
> what the remote's state is and to fetch the actual data. A third
> connection should only be needed if there are new tags to fetch, and
> that would be after some of the messages.
> 
> One of the changes in the upcoming release is to reduce this to one,
> except for an occasional second one.

The way to avoid multiple prompt for SSH password is to set up SSH key
infrastructure, so you can login using SSH keys which does not require
you to enter password, with the possible exception of adding key to
keyring if it is protected by password.

See ssh-add(1) and ssh-keygen(1) (and keychain(1) if you want to add
keyonce for all sessions).

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2008-03-29 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 15:44 why multiple password prompts? Paul
2008-03-29 16:48 ` Daniel Barkalow
2008-03-29 16:59   ` Jakub Narebski [this message]
2008-03-29 19:05     ` Daniel Barkalow
2008-03-29 18:37   ` Martin Langhoff
2008-03-29 18:49     ` Daniel Barkalow
2008-03-29 22:05     ` Jeff King
2008-03-29 22:11       ` Jeff King
2008-03-30 20:34   ` Bryan Donlan
2008-03-30 21:56     ` Daniel Barkalow
2008-03-30 22:05       ` Bryan Donlan

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=m37iflv54l.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=lists@pote.com \
    /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).