You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/23 19:11:16 UTC
[jira] [Commented] (SCM-832) maven-scm-provider-jgit should support
SSH public key auth
[ https://issues.apache.org/jira/browse/SCM-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347003#comment-15347003 ]
ASF GitHub Bot commented on SCM-832:
------------------------------------
GitHub user mkutter opened a pull request:
https://github.com/apache/maven-scm/pull/50
[SCM-832] maven-scm-provider-jgit should support SSH public key auth
Support for public key auth for ssh transfer is added by implementing a TransportConfigCallback and adding it to the session in all JGit Commands.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mkutter/maven-scm master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-scm/pull/50.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #50
----
commit 5f355e76fff3a9131d3b028570bcbc04964aaa40
Author: martin <ma...@fen-net.de>
Date: 2016-06-14T19:47:31Z
Support public key auth for SSH #SCM-832
Adds a TransportConfigCallback to all remote commands, which adds a public/private key based identity for repositories with ssh URLs if configured.
commit 4587b05d15664d8d70b672a964f7cb637d6bdf78
Author: martin <ma...@fen-net.de>
Date: 2016-06-14T20:06:27Z
Updated documentation for #SCM-832
commit 7f13f772448fd101b8fa76915f84e22599b5b343
Author: martin <ma...@fen-net.de>
Date: 2016-06-14T20:06:27Z
[SCM-832] Updated documentation
commit 3cbee487a4145a98390c5a7edcc5c78c9e7d5070
Author: martin <ma...@fen-net.de>
Date: 2016-06-14T20:16:28Z
Merge branch 'master' of github.com:mkutter/maven-scm
commit bf82d389c34b922fceccb6a8548fa08fb2e2e3f8
Author: martin <ma...@fen-net.de>
Date: 2016-06-23T17:51:36Z
Merge remote-tracking branch 'upstream/master'
commit 848e568a3c0cb1dd5c2f393cd4eaad598c0aa61d
Author: martin <ma...@fen-net.de>
Date: 2016-06-23T19:04:37Z
[SCM-832] Added debug logging
maven-scm-provider-jgit now outputs the private key used when run as mvn -X
----
> maven-scm-provider-jgit should support SSH public key auth
> ----------------------------------------------------------
>
> Key: SCM-832
> URL: https://issues.apache.org/jira/browse/SCM-832
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-gitexe, maven-scm-provider-jgit
> Affects Versions: 1.9.4
> Reporter: Martin Kutter
>
> The current mvn-scm-provider-jgit implementation does not support the explicit use of public key auth. The underlying implementation implicitly uses ~/id_rsa or ~/id_dsa if present (and not protected by a passphrase).
> For most Git repositories (Github, Gitlab, ...), public key authentication is mandatory for ssh access.
> This forces users to either use https, or to rely on a unprotected private key file.
> maven-scm-provider-jgit should support the privateKey and passphrase attributes available in server entries in maven settings.xml for ssh URLs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)