Yes, that worked like a charm! I did not know you could set the cipher that
way.
Many thanks!
- nick
----- Original Message -----
From: Atsuhiko Yamanaka <y...@jcraft.com>
To: nmori...@yahoo.com
Cc: jsch-users@lists.sourceforge.net
Sent: Tuesday, September 18, 2012 10:26 PM
Subject: Re: [JSch-users] Algorithm negotiation fail issue
Hi,
+-From: Nick Morizio <nmori...@yahoo.com> ------
|_Date: Tue, 18 Sep 2012 09:59:59 -0700 (PDT) __
|
|I am running into a problem connecting to a server with JSCH.? This worked
|until recently when the server was upgraded to more stringent security
|policies.
|
|The issue appears to be that aes256-ctr is required by the server,
|and JSCH is not reporting it as available during negotiation?? I have
|installed the "JCE Unlimited Strength Jurisdiction Policy" from Oracle
|correctly into my JVM, and it does appear to have access to all
| the ciphers.
|
|Here is the log output from Jsch:
...
How about invoking followings before Session#connect()?
session.setConfig("cipher.s2c", "aes256-ctr");
session.setConfig("cipher.c2s", "aes256-ctr");
Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
Skype callto://jcraft/
Twitter: http://twitter.com/ymnk
Facebook: http://facebook.com/aymnk
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
