You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2011/04/11 14:33:22 UTC
[jira] Moved: (WAGON-324) Site cannot be deployed when part of
release plugin, scp method used and server uses ECDSA
[ http://jira.codehaus.org/browse/WAGON-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl moved MSITE-580 to WAGON-324:
-------------------------------------------
Component/s: (was: site:deploy)
wagon-ssh
Affects Version/s: (was: 2.2)
Key: WAGON-324 (was: MSITE-580)
Project: Maven Wagon (was: Maven 2.x and 3.x Site Plugin)
> Site cannot be deployed when part of release plugin, scp method used and server uses ECDSA
> ------------------------------------------------------------------------------------------
>
> Key: WAGON-324
> URL: http://jira.codehaus.org/browse/WAGON-324
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Environment: Gentoo Linux, Maven 2.2.1
> Reporter: Rafal Figas
>
> When running mvn release:perform release plugin runs site-deploy. Configuration of distribution of site uses SCP protocol. So, when it comes to deploy a site SSH connection is being made. However "The authenticity of host [target_host] can't be established". What was strange I had no problems in calling "ssh target_host". There was no problem with establishing authenticity of host, neither with logging in using key. Due to this:
> http://jira.codehaus.org/browse/MRELEASE-424
> it was also impossible to answer the question about adding this key to ~/.ssh/known_hosts, so whole build just hang.
> What I noticed my known_hosts file contained something like:
> target_host ecdsa-sha2-nistp256 AAAAE2V[...]
> When I've replaced this entry with:
> target_host,10.0.0.2 ssh-rsa AAAAB3N[...]
> everything started working. Does that mean Release plugin (or Wagon, or JSCh?) cannot use ECDSA?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira