You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/06/03 19:28:39 UTC

[jira] [Resolved] (KARAF-3760) Can't ssh to Karaf when using the karaf-maven-plugin

     [ https://issues.apache.org/jira/browse/KARAF-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved KARAF-3760.
-----------------------------------------
    Resolution: Fixed

> Can't ssh to Karaf when using the karaf-maven-plugin
> ----------------------------------------------------
>
>                 Key: KARAF-3760
>                 URL: https://issues.apache.org/jira/browse/KARAF-3760
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.0.0.M2
>         Environment: Ubuntu 14.04, Java 7 and 8
>            Reporter: Lars Neumann
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.0.0.M3
>
>
> Seems like KARAF-3087 got lost on master.
> When I create a Karaf distribution using the karaf-maven-plugin the bin/karaf and bin/karaf.bat script get filtered by the maven-resources plugin. In my case JAVA_HOME gets replaced when creating a karaf-assembly.
> When I try to ssh to karaf using ssh -p 8101 karaf@localhost I get the same error as in KARAF-3087.
> {code}
> no matching cipher found: client aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se server 
> {code}
> Restoring the original karaf start script resolves the problem.
> Can this be fixed before the final 4.0.0 release?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)