Atsuhiko Yamanaka <ymnk@...> writes:

> 
> Hi,
> 
> On Tue, Jul 29, 2014 at 1:18 AM, Marc Logemann
> <marc.logemann@...> wrote:
> > we are using JSch as transport mechanism for EDI data to a different company
> > for about 7 years now. Today we upgraded to Java 8 and now when we try to
> > connect, we get:
> >
> >  Session.connect: java.security.InvalidKeyException: Key is too long for
> > this algorithm
> 
> Could you try
>   https://gist.github.com/ymnk/2318108#file-logger-java
> on Java7 and Java8?
> 
> 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
> Skype callto://jcraft/
> 
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls. 
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> 


We had a similar problem, though we are using java version 1.7
After upgrading java from version 1.7.0_55 to 1.7.0_71 the SFTP stopped
working with the exception mentioned; InvalidKeyException: Key is too long
for this algorithm.
We were using OpenJDK on CentOS 6 
And trying to update the JCE extension did not help
But after changing to Oracle's Java JDK version 1.7.0_71 the problem was
resolved, even without the JCE extension.
I hope this can help 





------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users

Reply via email to