-----Message d'origine----- De : Claus Ibsen [mailto:claus.ib...@gmail.com] Envoyé : 16 juillet 2017 03:16 À : users@camel.apache.org > > You should use the versions of the JARs that Apache Camel is built with. > > When you use Maven you get this "for free" here is what camel-ssh has a > dependency:tree
A simple (but devastating) constraint I must operate under is that I cannot use Maven. > [INFO] org.apache.camel:camel-ssh:jar:2.20.0-SNAPSHOT > [INFO] +- org.apache.camel:camel-core:jar:2.20.0-SNAPSHOT:compile > [INFO] | \- org.slf4j:slf4j-api:jar:1.7.22:compile > [INFO] +- org.apache.mina:mina-core:jar:2.0.16:compile > [INFO] +- org.apache.sshd:sshd-core:jar:0.14.0:compile > [INFO] +- org.bouncycastle:bcpg-jdk15on:jar:1.55:compile > [INFO] | \- org.bouncycastle:bcprov-jdk15on:jar:1.55:compile > [INFO] +- org.bouncycastle:bcpkix-jdk15on:jar:1.55:compile > [INFO] +- org.apache.camel:camel-test:jar:2.20.0-SNAPSHOT:test > [INFO] | \- junit:junit:jar:4.12:test > [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test > [INFO] +- org.apache.logging.log4j:log4j-api:jar:2.8.2:test > [INFO] +- org.apache.logging.log4j:log4j-core:jar:2.8.2:test > [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.8.2:test > [INFO] +- org.apache.camel:apt:jar:2.20.0-SNAPSHOT:provided > [INFO] | \- org.apache.camel:spi-annotations:jar:2.20.0-SNAPSHOT:provided > [INFO] +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile > [INFO] \- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile Putting these in the class path does the trick: camel-core-2.19.1.jar camel-ssh-2.19.1.jar slf4j-api-1.7.25.jar slf4j-simple-1.7.25.jar sshd-core-0.140.jar bcpg-jdk15on-157.jar bcpkix-jdk15on-157.jar bcprov-jdk15on-157.jar (The bouncycastle jars were obtained from https://www.bouncycastle.org/download/crypto-157.zip) The remaining jars (mina-core-2.0.16, camel-test-2.20.0, junit-4.12, hamcrest-core-1.3, log4j-api-2.8.2, log4j-core-2.8.2, log4j-slf4j-impl-2.8.2, apt-2.20.0, spi-annotations-2.20.0, jaxb-core-2.2.11, jaxb-impl-2.2.11) may be needed if/when other features of camel get called upon, I guess. I find it bizarre that Camel 2.19 would still rely on sshd-core-0.16.0 (dating back to early 2015) while sshd-core has moved on to 1.6.0. When will the migration occur? On a different tack, the code yields in part this warning message: [sshd-SshClient[5be46f9d]-nio2-thread-1] WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at /<host>:<port> presented unverified EC key: ac:...:6a Is there any way to get rid of this? I'd have expected a known_hosts option for camel-ssh, but there isn't one. Daniel U. Thibault, M.Sc.² Computer Scientist, MCCS-SPC, Valcartier Research Centre Defence Research and Development Canada / Government of Canada
