[
https://jira.codehaus.org/browse/WAGON-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356489#comment-356489
]
Anthony Whitford edited comment on WAGON-413 at 11/20/14 3:04 PM:
------------------------------------------------------------------
Are there any outstanding questions? _(If so, I can try to acquire some more
background data.)_
It looks like the code added to
{{wagon-providers/wagon-ssh/src/main/java/org/apache/maven/wagon/providers/ssh/jsch/AbstractJschWagon.java}}
from WAGON-403 just needs to be moved down to be part of the _else_ clause so
that a private key is used if specified.
Can this be scheduled as part of 2.9?
was (Author: awhitford):
Are there any outstanding questions? _(If so, I can try to acquire some more
background data.)_
Can this be scheduled as part of 2.9?
> Private Key authentication is no longer working with wagon-ssh-2.6
> ------------------------------------------------------------------
>
> Key: WAGON-413
> URL: https://jira.codehaus.org/browse/WAGON-413
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Affects Versions: 2.6
> Environment: Windows, Maven 3.0.4, Java 7 64-bit
> Reporter: Anthony Whitford
> Priority: Blocker
>
> I have to provide the {{wagon-ssh}} dependency to the {{maven-site-plugin}}
> in order to upload the site via {{scp}}. Authentication for the {{scp}} is
> done via an _SSH key_.
> Version 2.5 works fine, but when I upgrade to version 2.6, I am now getting a
> Password prompt, and then a _Connection Refused_. (The Private Key should
> negate a password prompt.)
> With version 2.6, I get BUILD FAILURE:
> {noformat}
> [INFO] --- maven-site-plugin:3.3:deploy (default-deploy) @ project ---
> Using private key: C:\Users\BuildAgent\.ssh\id_rsa
> Password for buildagent@mvnsitehost:
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/ - Session: Connection
> refused
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/ - Session:
> Disconnecting
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/ - Session:
> Disconnected
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {noformat}
> With version 2.5, I get BUILD SUCCESS:
> {noformat}
> [INFO] --- maven-site-plugin:3.3:deploy (default-deploy) @ project ---
> Using private key: C:\Users\BuildAgent\.ssh\id_rsa
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/ - Session: Opened
> [INFO] Pushing D:\BuildAgent\projects\Project\Build_Snapshot\target\site
> [INFO] >>> to scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/./
> Executing command: mkdir -p "/opt/maven/sites/project/3.4-SNAPSHOT/./"
> Executing command: mkdir -p "/opt/maven/sites/project/3.4-SNAPSHOT/."
> Executing command: scp -t
> "/opt/maven/sites/project/3.4-SNAPSHOT/./wagon4279752042048724778.zip"
> Uploading: ./wagon4279752042048724778.zip to
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/
>
>
> ##############################################################################
> Transfer finished. 316495 bytes copied in 0.031 seconds
> Executing command: cd "/opt/maven/sites/project/3.4-SNAPSHOT/./"; unzip -q
> -o "wagon4279752042048724778.zip"; rm -f "wagon4279752042048724778.zip"
> Executing command: chmod -Rf g+w,a+rX /opt/maven/sites/project/3.4-SNAPSHOT/
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/ - Session:
> Disconnecting
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/ - Session:
> Disconnected
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> {noformat}
> So, clearly the _new behavior_ is the _Connection Refused_:
> {noformat}
> Password for buildagent@mvnsitehost:
> scp://mvnsitehost/opt/maven/sites/project/3.4-SNAPSHOT/ - Session: Connection
> refused
> {noformat}
> (?) Could version 2.6 have broken the private key logic?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
