[
https://issues.apache.org/jira/browse/SCM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963876#comment-17963876
]
ASF GitHub Bot commented on SCM-992:
------------------------------------
jira-importer commented on issue #1216:
URL: https://github.com/apache/maven-scm/issues/1216#issuecomment-2964657004
**[Konrad
Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)**
commented
Yes, the `GIT_SSH_COMMAND` approach is already leveraged in
https://github.com/apache/maven-scm/pull/153 for testing SSH authentication. It
is supported since git 2.3.0.
> Support explicitly configured SSH private key for gitexe provider
> -----------------------------------------------------------------
>
> Key: SCM-992
> URL: https://issues.apache.org/jira/browse/SCM-992
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
> Reporter: Konrad Windszus
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> Currently the {{privateKey}} parameter set on
> {{ScmProviderRepositoryWithHost}} is only evaluated in provider "jgit". It
> should also be used for provider "git". Same for {{passphrase}} parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
