[ https://issues.apache.org/jira/browse/CAMEL-11611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123340#comment-16123340 ]
Sascha Dirbach commented on CAMEL-11611: ---------------------------------------- Hi, I will have a look into this. Sascha > Add a knownHosts option to the camel-ssh component > -------------------------------------------------- > > Key: CAMEL-11611 > URL: https://issues.apache.org/jira/browse/CAMEL-11611 > Project: Camel > Issue Type: Improvement > Components: camel-ssh > Affects Versions: Future > Environment: Any. > Reporter: Daniel U. Thibault > Priority: Minor > Labels: known_hosts, ssh > Fix For: Future > > > Currently, when one uses camel-ssh to connect to some server, one gets this > message: > [sshd-SshClient[5be46f9d]-nio2-thread-1] WARN > org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at > /<host>:<port> presented unverified EC key: ... > This is an annoyance that would readily be gotten rid of by adding a > knownHosts option similar to certResource: > * name: knownHosts > * default value: null > * description: Path reference to a the list of known hosts public key > certificates (typically ~/.ssh/known_hosts). Prefix path with classpath:, > file:, or http:. > This value would be used by StaticServerKeyVerifier.java to avoid issuing the > warning (as appropriate). com.jcraft.jsch.JSch uses this through its > setKnownHosts method. -- This message was sent by Atlassian JIRA (v6.4.14#64029)