\u547d\u4ee4\u884c\u4e0bgit\u4e00\u5207\u6b63\u5e38\uff0ceclipse\u51fa\u73b0auth fail\u9519\u8bef\uff0c
\n\u9700\u8981\u6dfb\u52a0 GIT_SSH=\/usr\/bin\/ssh<\/p>\n
\u539f\u6587\uff1a<\/p>\n
I had exactly same problem but I found the cure from a Eclipse bug report!<\/p>\n
An environment variable named GIT_SSH must be set with a path to a ssh executable [1].<\/p>\n
For example on Ubuntu Linux (10.10 64bit):<\/p>\n
> export GIT_SSH=\/usr\/bin\/ssh
\n> eclipse
\nAfter that pushes to GitHub repository work like they should. I tested this with Eclipse Galileo and Indigo.<\/p>\n
The problem is really annoying and the solution is far from nice. For now, making the solution permanent for, at least Ubuntu users, one must make the env variable permanent. It can be done by adding the export command to ~\/.profile or ~\/.bashrc [2]. For example:<\/p>\n
> cd ~
\n> echo “export GIT_SSH=\/usr\/bin\/ssh” >> .profile
\nAnd then restart Eclipse to take effect.<\/p>\n","protected":false},"excerpt":{"rendered":"
\u547d\u4ee4\u884c\u4e0bgit\u4e00\u5207\u6b63\u5e38\uff0ceclipse\u51fa\u73b0auth fail\u9519\u8bef\uff0c \u9700\u8981\u6dfb\u52a0 G …<\/p>\n