[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/12/11 10:59 AM: ------------------------------------------------------------------- There's another problem when pushing in eclipse egit that affects systems where the key was generated using AES-128 - newer linux systems, newer putty's): 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-128 encryption ((read all the details here: http://www.eclipse.org/forums/index.php/t/207710/): * https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526 * http://protodave.com/tips/eclipse-egit-github-jsch-and-aes-128-encrypted-... 1) You have to solve this either by updating the JSch bundle to 0.1.44 from the eclipse orbit update site: http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r... If you have the egit source checked out you'd furthermore have to make sure that you would not include the jsch 0.1.41 bundle in your workspace. You have to close com.jcraft.jsch or remove it from your workspace (you most likely ended using the egit contributor guide http://wiki.eclipse.org/EGit/Contributor_Guide#Adding_a_remote -> "Libraries from Orbit". JSch 0.1.41 gets installed to your workspace if you import the egit team project set or install the 3rd party dependencies manually). The problem seems to be that the plugin in your workspace has precendence compared to the ones installed in your target workspace. Your Test IDE (the one you start when testing the egit source code) will end up having jsch 0.1.41 only. * Host IDE has both jsch bundles (0.1.41 and 0.1.44): !host-ide-jsch-0141.png! * Test IDE has jsch only in version 0.1.41: !client-ide-jsch-0141.png! OR 2) 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 systems where the key was generated using AES-128 - newer linux systems, newer putty's): 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-128 encryption ((read all the details here: http://www.eclipse.org/forums/index.php/t/207710/): * https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526 * http://protodave.com/tips/eclipse-egit-github-jsch-and-aes-128-encrypted-... 1) You have to solve this either by updating the JSch bundle to 0.1.44 from the eclipse orbit update site: http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r... If you have the egit source checked out you'd furthermore have to make sure that you would not include the jsch 0.1.41 bundle in your workspace. You have to close com.jcraft.jsch or remove it from your workspace (you most likely ended using the egit contributor guide http://wiki.eclipse.org/EGit/Contributor_Guide#Adding_a_remote -> "Libraries from Orbit". JSch 0.1.41 gets installed to your workspace if you import the egit team project set or install the 3rd party dependencies manually). The problem seems to be that the plugin in your workspace has precendence compared to the ones installed in your target workspace. Your Test IDE (the one you start when testing the egit source code) will end up having jsch 0.1.41 only. OR 2) 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