[
https://issues.apache.org/jira/browse/SCM-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964659#comment-17964659
]
Olivier Lamy commented on SCM-477:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#694|https://github.com/apache/maven-scm/issues/694].
> Public key passphrases when using ext connection method
> -------------------------------------------------------
>
> Key: SCM-477
> URL: https://issues.apache.org/jira/browse/SCM-477
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-cvs
> Affects Versions: 1.3
> Environment: Windows
> Reporter: mattb
> Priority: Major
>
> When using the ext connection method, and a public key is found by the
> cvsjava implementation, it checks a System property named
> "maven.scm.cvs.java.ssh.passphrase". If this property is not defined, then
> the empty string is used as the passphrase.
> The exception given when attempting to use the public key with an empty
> passphrase (when in reality the passphrase is not empty) is misleading and
> does not really tell the user that the cvsjava library could not determine
> what passphrase to use. In addition, the site documentation does not make any
> mention of the need to set the property "maven.scm.cvs.java.ssh.passphrase".
> In my opinion, a mention in the site provider documentation about this
> property (along with several others used by ExtConnection, such as the
> location of the public key file, which are all undocumented) would go a long
> way towards helping make this plugin/provider easier to use. In addition, the
> exception printed in this scenario could be clearer as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
