Am 11.09.2014 13:04, schrieb Nick: > Also the following test passes fine without any exception: [...] >> String cryptoAlg = "AES";
change that to "AES256" and try again. Make sure that you use the same JVM with this test as you use for your JSCH-call. Your JMV might implicitly use AES-64 since we haven't specified the length. > JSch logs failed.txt [...] > aes256-cbc is not available. > aes192-cbc is not available. [...] > kex: server->client aes128-cbc hmac-md5 none > kex: client->server aes128-cbc hmac-md5 none The server only accepts CBC-based ciphers that are not available with this JVM. > JSch logs success.txt [...] > aes256-cbc is not available. > aes192-cbc is not available. [...] > kex: server->client aes128-ctr hmac-md5 none > kex: client->server aes128-ctr hmac-md5 none Here the server also allows CTR-based ciphers that the JVM allows as well. My bet still is on the missing policy files. But Java8 seems to allow a bit more than previous JVMs (the above test was based on). Cheers, Lothar ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ JSch-users mailing list JSch-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jsch-users
