[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-9511) Openshift Express: create egit action that commits and pushes in 1 step

[ https://issues.jboss.org/browse/JBIDE-9511?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9511 at 8/11/11 3:11 PM: ------------------------------------------------------------------ There's another problem when pushing in eclipse egit that affects systems where the key was not generated in eclipse (ssh-keygen, putty): Your passphrase to is not accepted when you push (passphrase dialog keeps showing up, feels like your passphrase is invalid). Strange enough, pushing works in the command line. The problem is caused by the JSch library which does not support AES encryption: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526 * http://protodave.com/tips/eclipse-egit-github-jsch-and-aes-128-encrypted-... (read all the details here: http://www.eclipse.org/forums/index.php/t/207710/) You have to solve this either by updating the JSch bundle to 0.1.41 from the eclipse orbit update site: http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r... Alternatively you can also instruct egit to use an external ssh implementation, the ssh command line for instance. To achieve this you'd have to set the GIT_SSH environment variable to point to your ssh command: {code} export GIT_SSH=/usr/bin/ssh {code} was (Author: adietish): There's another problem when pushing in eclipse egit that affects linux systems: Your passphrase to is not accepted when you push (passphrase dialog keeps showing up, feels like your passphrase is invalid). Strange enough, pushing works in the command line. The problem is caused by the JSch library which does not support AES encryption: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526 * http://protodave.com/tips/eclipse-egit-github-jsch-and-aes-128-encrypted-... You have to solve this either by updating the JSch bundle to 0.1.41 from the eclipse orbit update site: http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r... Alternatively you can also instruct egit to use an external ssh implementation, the ssh command line for instance. To achieve this you'd have to set the GIT_SSH environment variable to point to your ssh command: {code} export GIT_SSH=/usr/bin/ssh {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira