[
https://issues.apache.org/jira/browse/SCM-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963304#comment-17963304
]
ASF GitHub Bot commented on SCM-832:
------------------------------------
jira-importer commented on issue #1052:
URL: https://github.com/apache/maven-scm/issues/1052#issuecomment-2964642962
**[Konrad
Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)**
commented
I am also affected from that. The PR IMHO looks good, but I think it would
be good if the passphrase could not only be entered in the `settings.xml` but
is alternatively used the given credentials (that way it would be possible to
use `mvn release:prepare -Dpassword=<SSH private key passphrase>`).
> 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 (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-provider-gitexe, maven-scm-provider-jgit
> Affects Versions: 1.9.4
> Reporter: Martin Kutter
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.11.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
