OK, I built a jar from this version using your build.xml, and tested it successfully in the following situations:
A) Production environment, via a diagnostic tool, against the server with the long keys.
B) Development environment, using an automated regression test tool, which exercises our entire application through about 80 test scenarios. This basically uses the SFTP feature of JSch, specifically doing list, get, put and delete.
So your fix looks fine! Roll on v0.1.25!
----- Original Message -----
From: ymnk@... (Atsuhiko Yamanaka)
Date: Monday, January 30, 2006 12:34 pm
Subject: Re: [JSch-users] Arbitrary Limit on length of host key fingerprint?
> +-From: cameron.smith@... -----
> |_Date: Mon, 30 Jan 2006 12:12:34 +0200 __
> |The limit is in fact set on line 69 of KnownHosts.java, and it
> |appears to be arbitrary - i.e. there is no underlying
> restriction in JSch.
> | We tried altering this value to 2048 in the JSch source.
> | byte buf=new byte;
> |And it appears to be working in the context of our
> application. Would it be possible to include this change in a
> future version of JSch?
> That problem has been fixed in http://www.jcraft.com/jsch/jsch-
> Please try it.
> Atsuhiko Yamanaka
> 4-1 OHMACHI 1-CHOME AOBA-KU,
> SENDAI, MIYAGI 980-0804 Japan.
> Tel +81-22-723-2150
> Fax +81-22-224-8773
> Skype callto://jcraft/