[jbosstools-issues] [JBoss JIRA] (JBIDE-10664) Cannot deploy GWT project to OpenShift: SSH key problems

[ https://issues.jboss.org/browse/JBIDE-10664?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10664 at 1/18/12 10:42 AM: -------------------------------------------------------------------- @Malte: What captures my attention is the following when you try to clone the remote repository: {code} Caused by: org.eclipse.jgit.errors.NoRemoteRepositoryException: ssh://c7376e4494f9452ebcc7e6b6121c3208@osgwt-brandsmill.rhcloud.com/~/git/osgwt.git/: Host key verification failed. {code} This pretty much makes me think that your local ssh executable has troubles dealing with the ssh-key (http://stackoverflow.com/questions/3516719/hudson-git-error-ssh). So I'd go on trying to find out what's wrong with your key: * what tool did you use to create your key? * what type is your key of? (first line in the private key, it would specify something like DEK-Info: DES-EDE3-CBC,EA2C33B68ED7C5F2) Further checks: * In your current setup, that uses an external ssh executable: Can you clone the OpenShift repo with EGit? (get the Git Url from the Details of your OpenShift app in the OpenShift Application wizard and use it to clone the repo with EGit - proceed as described here: https://issues.jboss.org/browse/JBIDE-10563?focusedCommentId=12653788&... * Can you clone the repository with other tools (command-line etc.)? JSch *0.1.44* obviously still had issues reading AES type keys: http://www.jcraft.com/jsch/ChangeLog: {quote} bugfix: KeyPair.load can not handle private keys cyphered with AES. FIXED {quote} So another approach would be to unset GIT_SSH, install JSch *0.1.45* and try cloning. was (Author: adietish): @Malte: What captures my attention is the following when you try to clone the remote repository: {code} Caused by: org.eclipse.jgit.errors.NoRemoteRepositoryException: ssh://c7376e4494f9452ebcc7e6b6121c3208@osgwt-brandsmill.rhcloud.com/~/git/osgwt.git/: Host key verification failed. {code} This pretty much makes me think that your local ssh executable has troubles dealing with the ssh-key. So I'd go on trying to find out what's wrong with your key: * what tool did you use to create your key? * what type is your key of? (first line in the private key, it would specify something like DEK-Info: DES-EDE3-CBC,EA2C33B68ED7C5F2) Further checks: * In your current setup, that uses an external ssh executable: Can you clone the OpenShift repo with EGit? (get the Git Url from the Details of your OpenShift app in the OpenShift Application wizard and use it to clone the repo with EGit - proceed as described here: https://issues.jboss.org/browse/JBIDE-10563?focusedCommentId=12653788&... * Can you clone the repository with other tools (command-line etc.)? JSch *0.1.44* obviously still had issues reading AES type keys: http://www.jcraft.com/jsch/ChangeLog: {quote} bugfix: KeyPair.load can not handle private keys cyphered with AES. FIXED {quote} So another approach would be to unset GIT_SSH, install JSch *0.1.45* and try cloning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira