Marc Logemann
2014-07-28 16:18:26 UTC
Hi,
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
Currently we use:
<dependency org="com.jcraft" name="jsch" rev="0.1.42"/>
Our code is like this..
Session session = jsch.getSession(sftpUser, sftpHost);
session.setPassword(sftpPassword);
UserInfo ui = new SFTPClientWrapper.MyUserInfo();
session.setUserInfo(ui);
session.connect();
So some questions arise :-)
1) will upgrade to latest version of JSch help me?
2) do you know the error in general? I dont have any clue because i dont do
anything with keys. IMO its some kind of internal issue with java and JSch.
Thanks for any hints.
Marc
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
Currently we use:
<dependency org="com.jcraft" name="jsch" rev="0.1.42"/>
Our code is like this..
Session session = jsch.getSession(sftpUser, sftpHost);
session.setPassword(sftpPassword);
UserInfo ui = new SFTPClientWrapper.MyUserInfo();
session.setUserInfo(ui);
session.connect();
So some questions arise :-)
1) will upgrade to latest version of JSch help me?
2) do you know the error in general? I dont have any clue because i dont do
anything with keys. IMO its some kind of internal issue with java and JSch.
Thanks for any hints.
Marc