Is there a way to turn on low level logging so we can see why Camel is failing to connect? We can connect to the same server with puttyftp and put files but not with camel...and the errors are not very detailed.
-Dave On Fri, Mar 3, 2017 at 9:54 AM, S AR <sa_remin...@hotmail.com> wrote: > Hello David, > > When I work with camel-sftp, The first thing I do is to manually connect > to the remote machine via ssh, so that my knownHosts > (System.getProperty(user.home)/.ssh/known_hosts) file is written. On > windows, I use cygwin for that. I assume you can do the same with putty. > > > You specify the certificate file as an option, as described in the > documentation: http://camel.apache.org/ftp2.html > > knownHostFile: path to your known_hosts > > privateKeyFile: path to your id_rsa > > > privateKeyFilePassphrase: passphrase of you id_rsa > > > Hope it gives you an idea about where to look at. > > > Good luck. > > > On 03.03.2017 17:32, David Hoffer wrote: > > How does Camel handle the SSH cert when connecting to SFTP servers? > Somehow it has to accept the cert provided by the server how does it do > that? > > The docs say the default is: > strictHostKeyChecking=no > > What does this mean? Does this mean it will accept every cert? > > What does strictHostKeyChecking=yes mean? > > Where does Camel store the cert that it accepted? Can we preempt this hole > process by manually accepting the cert with a different tool, eg. > puttyftp? In this case there would have to be a shared location for the > cert...we are running camel on Windows so I think puttyftp stores the cert > in the registry. Where does Camel/JSCH look for certs? > > -Dave > > > >
