[
https://issues.apache.org/jira/browse/SCM-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963771#comment-17963771
]
ASF GitHub Bot commented on SCM-945:
------------------------------------
jira-importer opened a new issue, #1175:
URL: https://github.com/apache/maven-scm/issues/1175
**[Konrad
Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)**
opened
**[SCM-945](https://issues.apache.org/jira/browse/SCM-945?redirect=false)** and
commented
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.
---
**Affects:** 1.11.2
**Issue Links:**
- [SCM-993](https://issues.apache.org/jira/browse/SCM-993) Add tests for SSH
private key-based authentication during checkout (clone)
(_**"blocks"**_)
- [SCM-995](https://issues.apache.org/jira/browse/SCM-995) Upgrade JGit to
5.13.1 and leverage Apache Mina SSHD instead of JSch
(_**"depends upon"**_)
**Remote Links:**
- [GitHub Pull Request #153
](https://github.com/apache/maven-scm/pull/153)
> Support OpenSSH private keys with maven-scm-provider-jgit
> ---------------------------------------------------------
>
> Key: SCM-945
> URL: https://issues.apache.org/jira/browse/SCM-945
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-jgit
> Affects Versions: 1.11.2
> Reporter: Konrad Windszus
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> 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.20.10#820010)
