Hello Atsuhiko, > By the default, jsch does not support the ciphers aes*-cbc, > but it can handle them on J2SE 1.4.2(or later). > Please refer to > http://www.jcraft.com/jsch/examples/AES.java
Does this mean that in order to be most compatbile, any Jsch application that knows it's running on an 1.4 or later JVM should include code like this: java.util.Hashtable config=new java.util.Hashtable(); config.put("cipher.s2c", "aes128-cbc,3des-cbc,blowfish-cbc"); config.put("cipher.c2s", "aes128-cbc,3des-cbc,blowfish-cbc"); session.setConfig(config); this is important for us as our Eclipse based application is known to run on Java 1.4 or later, and we'd like to be most compatible. Can there be any negative side-effect of adding that config? Would would happen if that code were in an application but the JVM does not support AES? Why is AES disabled by default in Jsch? Thanks, -- Martin Oberhuber Wind River Systems, Inc. Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ JSch-users mailing list JSch-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jsch-users