On Sat, 29 Mar 2008, Jakub Narebski wrote: > Daniel Barkalow <barkalow@xxxxxxxxxxxx> writes: > > > On Sat, 29 Mar 2008, Paul wrote: > > Paul who? How should I know? > >> 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. Sure, but it's inconvenient to wrap git-fetch and git-pull in ssh-agent/ssh-add/kill if you want to get exactly one password prompt per logical remote-using operation. Personally, I like that when I do operations involving authorized access to a remote machine, I need to enter my password. But once per command is all I want. -Daniel *This .sig left intentionally blank* -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
