You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/10/09 10:12:00 UTC

[jira] [Commented] (SCM-945) Support OpenSSH private keys with maven-scm-provider-jgit

    [ https://issues.apache.org/jira/browse/SCM-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210792#comment-17210792 ] 

Michael Osipov commented on SCM-945:
------------------------------------

I have briefly followed the discussion over the years. I consider JSch to be completely dysfunctional for a long time. What is the upshot? Which SSH client implementation are they using? What would it take to make JGit with SCM use SSHEXE?

> Support OpenSSH private keys with maven-scm-provider-jgit
> ---------------------------------------------------------
>
>                 Key: SCM-945
>                 URL: https://issues.apache.org/jira/browse/SCM-945
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-jgit
>    Affects Versions: 1.11.2
>            Reporter: Konrad Windszus
>            Priority: Major
>
> For SSH based authentication with private keys in the OpenSSH format the following error is being emitted:  {{invalid privatekey: ...}}
> This is due to the use of JGit 4.5.4 (https://github.com/apache/maven-scm/blob/c5eb2c187568809e0dc0ea9ac83031f1dcb5ad1a/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/pom.xml#L53) which used JSch which lacks support for those private keys. JGit 5.2 comes with a new SSH implementation (https://bugs.eclipse.org/bugs/show_bug.cgi?id=520927) and should by that also support OpenSSH private keys.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)