Hi, +-From: "Oberhuber, Martin" <[EMAIL PROTECTED]> -- |_Date: Thu, 2 Aug 2007 18:55:27 +0200 ________________________ | |thanks for your answer. Yes I will likely file an Eclipse Bugzilla bug |for this. Just wondering, why couldn't the core jsch library try and |auto-detect what algorightms are available?
It will be easy to check the availability of AES in jsch, but I'm not planing to do at the present time. As you can see at rfc2533[1], "3des-cbc" is REQUIRED and, IMHO, that problem comes from the fault of that admin who dropped the "3des-cbc" support without understanding what that means. Almost of all users will not have such problems in connecting to SSHDs, which are managed by usual admins and it is just a waist of CPU time for those users to check if AES is available or not. As rfc2533[1] states, "3des-cbc" will be not REQUIRED at some future time, we may need to check the availability of AES in jsch. If you and others have strong and reasonable counter arguments or suggestions, it may be checked in jsch. [1] http://tools.ietf.org/html/rfc4253 Sincerely, -- Atsuhiko Yamanaka JCraft,Inc. 1-14-20 HONCHO AOBA-KU, SENDAI, MIYAGI 980-0014 Japan. Tel +81-22-723-2150 +1-415-578-3454 Fax +81-22-224-8773 Skype callto://jcraft/ ------------------------------------------------------------------------- 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
