Community
Participate
Working Groups
Eclipse EGit 1.0.0.201106081625-r org.eclipse.egit.feature.group Eclipse EGit Eclipse JGit 1.0.0.201106081625-r org.eclipse.jgit.feature.group Eclipse JGit It seems impossible to get the UI to save / remember the password. The egit UI then prompts 3 times while trying to push through the UI. I tried Configure Push from the repositories view and entered my password on the Destination Git Repository Page and ticked "Store in Secure Store", but this doesn't seem to work. The result is that a fetch followed by a push prompts 4 times for a password :(
Which protocol did you use here ? If you used ssh there are some patches underway http://egit.eclipse.org/r/#change,3796 http://egit.eclipse.org/r/#change,3595 and http://egit.eclipse.org/r/#change,3594
This affects all platforms, not just Linux. Can the platform field be updated to reflect this? Secondly, it's a pretty major blocker to using EGit against SSH backed repositories that don't use public key encryption. I note the reviews listed here haven't been all completed - what is the current state of this bug? Will it be fixed for the EGit 1.1 release with Indigo SR1 next month?
Same problem for me on Linux (Ubuntu 11.04) using ssh to push on sourceforge.
I think the following change submitted on July 5 and included in EGit 1.1 should fix this : http://egit.eclipse.org/r/#change,3796 Could you retry with EGit 1.1 or a recent nightly build ?
I keep seeing the same with the latest EGit (1.3.0), in my case using the "Pull" command from the Git Command Group. I have debugged some and ended up deep in JSch. The com.jcraft.jsch.UserAuthPublicKey.start(Session) method calls java.io.IdentityFile.setPassPhrase(byte[]). There in line 398, the decrypt() method returns false which results in the setPassPhrase method to return false as well which in turn triggers the retries. Unfortunately, this is not happening always...
What I also wanted to mention that I don't see the problem with the normal Fetch command.
*** Bug 352752 has been marked as a duplicate of this bug. ***