This was on Java 11 btw. On Wed, Aug 10, 2022 at 11:38 AM Jeremy Ross <jeremy.g.r...@gmail.com> wrote:
> Also, there are endpoint parameters for these settings, but I can't get > camel to accept them: > > There are 2 parameters that couldn't be set on the endpoint. Check the uri > if the parameters are spelt correctly and that they are properties of the > endpoint. Unknown > parameters=[{publicKeyAcceptedAlgorithms=ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa, > serverHostKeys=ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa}] > > On Tue, Aug 9, 2022 at 11:30 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > >> On Tue, Aug 9, 2022 at 10:37 PM Jeremy Ross <jeremy.g.r...@gmail.com> >> wrote: >> >> > I had to enable ssh-rsa keys and the following to KEXs that the server >> > supported. Added this to a static block in my application. >> > >> > JSch.setConfig("server_host_key", JSch.getConfig("server_host_key") + >> > ",ssh-rsa"); >> > JSch.setConfig("PubkeyAcceptedAlgorithms", JSch.getConfig( >> > "PubkeyAcceptedAlgorithms") + ",ssh-rsa"); >> > JSch.setConfig("kex", JSch.getConfig("kex") + >> > ",diffie-hellman-group1-sha1,diffie-hellman-group14-sha1"); >> > >> > Should I add this to the migration guide? >> > >> > >> Yes you are welcome to do that. Also can you write which JVM version you >> were using? >> >> >> > Jeremy >> > >> > On Mon, Jul 25, 2022 at 12:26 AM Claus Ibsen <claus.ib...@gmail.com> >> > wrote: >> > >> > > Hi >> > > >> > > Did you find out about the algorithms with the newer JAR or did you >> just >> > > keep using the old JSCH client? >> > > I think feedback here is valuable for other users. >> > > >> > > And we should add a note in the 3.18 upgrade guide about this so >> others >> > can >> > > take notice ahead of time before upgrading. >> > > https://camel.apache.org/manual/camel-3x-upgrade-guide-3_18.html >> > > >> > > On Wed, Jul 13, 2022 at 10:24 AM Grzegorz Grzybek < >> gr.grzy...@gmail.com> >> > > wrote: >> > > >> > > > Hello >> > > > >> > > > https://issues.apache.org/jira/browse/CAMEL-17835 issue was about >> > > > switching >> > > > from unmaintained version of jsch to new forked version with more >> > (safer) >> > > > alogorithms supported (like SHA2 and eddsa). >> > > > >> > > > You'd have to enable server side and Camel debug logging to check >> which >> > > KEX >> > > > algorithms are presented by Camel and which are offered by the >> server. >> > > > >> > > > kind regards >> > > > Grzegorz Grzybek >> > > > >> > > > śr., 13 lip 2022 o 10:17 Reto Peter <reto.pe...@advanceit.ch> >> > > napisał(a): >> > > > >> > > > > Hi >> > > > > >> > > > > In Camel 3.16.0 we did successfully use the SFTP component like >> this: >> > > > > >> > > > > >> > > > >> > > >> > >> from("sftp://{{sftp.host}}:{{sftp.port}}/{{sftp.remotedir.from.customer}}" >> > > > > + "?username={{sftp.username}}" >> > > > > + "&password={{sftp.password}}" >> > > > > + >> > > > > "&useUserKnownHostsFile=false&delete=true&delay=30000") >> > > > > >> > > > > The version of the lib used was jsch-0.1.55.jar >> > > > > >> > > > > >> > > > > After upgrading to Camel 3.18.0 we got errors like this: >> > > > > >> > > > > >> org.apache.camel.component.file.GenericFileOperationFailedException: >> > > > > Cannot connect to sftp://xxx.com@xxx.hosting:5544 >> > > > > Caused by: com.jcraft.jsch.JSchException: Algorithm negotiation >> fail >> > > > > at >> > > > com.jcraft.jsch.Session.receive_kexinit(Session.java:604) >> > > > > at com.jcraft.jsch.Session.connect(Session.java:334) >> > > > > at >> > > > > >> > > > >> > > >> > >> org.apache.camel.component.file.remote.SftpOperations.tryConnect(SftpOperations.java:160) >> > > > > at >> > > > > >> > > >> org.apache.camel.support.task.ForegroundTask.run(ForegroundTask.java:92) >> > > > > at >> > > > > >> > > > >> > > >> > >> org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:135) >> > > > > >> > > > > The lib used was jsch-0.2.1.jar >> > > > > >> > > > > After replacing the new with the old library jsch-0.1.55.jar, >> > > everything >> > > > > works again >> > > > > Any idea? >> > > > > >> > > > >> > > >> > > >> > > -- >> > > Claus Ibsen >> > > ----------------- >> > > http://davsclaus.com @davsclaus >> > > Camel in Action 2: https://www.manning.com/ibsen2 >> > > >> > >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> >