Hi,
I'm developing a grid computing application.
I had decided use jsch for file transfering. I wrote a simple program for
file transfer.
When I execute the program, I found the next log output:
INFO:
CheckCiphers: aes256-cbc,aes192-cbc,aes128-cbc
INFO:
aes256-cbc is not available.
INFO:
aes192-cbc is not available.
INFO:
SSH_MSG_KEXINIT sent
INFO:
SSH_MSG_KEXINIT received
INFO:
kex: server->client aes128-cbc hmac-md5 none
INFO:
kex: client->server aes128-cbc hmac-md5 none
The client and server start to communicate with the aes128-cbc protocol.
Now, when I try to integrate the transfer module with my grid application
the logger output looks different:
INFO:
CheckCiphers: aes256-cbc,aes192-cbc,aes128-cbc
INFO:
aes256-cbc is not available.
INFO:
aes192-cbc is not available.
INFO:
aes128-cbc is not available.
INFO:
SSH_MSG_KEXINIT sent
INFO:
SSH_MSG_KEXINIT received
INFO:
kex: server->client 3des-cbc hmac-md5 none
INFO:
kex: client->server 3des-cbc hmac-md5 none
Caught: java.lang.ClassCastException:
at scp.run(scp.groovy:5)
at scp.main(scp.groovy)
The grid application requires to include the cog-jglobus.jar file. I
figure out, for including that .jar the aes128-cbc is unavailable and
enforce to use the 3des protocol provoking the abnormal exit.
How to avoid that annoying behavior?
Thanks a lot.
PD: If you need more information don't hesitate to ask me.
http://ece.uprm.edu/~s047267
http://del.icio.us/josanabr
http://blog-grid.blogspot.com
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
