Am 02.04.20 um 09:20 schrieb Richard Beare: > Hi, > Thanks for the reply. > > My suspicion is that the kex err is due to the PaloAltoNetworks stuff. If I > log into the remote workstation: > > sshd -T > > kexalgorithms > curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1 > > I guess the only fix will be extra kex options in libssh...
If I were you, I would talk to the folks that set up this PaloAltoNetworks device. To me, it looks like it should be upgraded/reconfigured so it speaks the same kex algorithms as your workstation. > Thanks for the tip on the proxy. If I create tunnel from localhost:2222 => > remote host sshd port, and configure the x2goclient to find the ssh proxy at > localhost:2222, then it appears to work, and hopefully that is one less > encryption layer. No. The layers remain. Once done right, you're just saving yourself the trouble of having to start the tunnel manually. But, again, your actual issue is something else. Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
