well my UserInfo implementation is just a stub class with setters and
getters for the hostname, user & pass. The user does not receive a separate
prompt for the password. I.E. MyUserInfo info = new MyUserInfo("some
hostname", "some user", "some pass")
the method getPassword() returns this.pass which was set in the constructor.
My testcase is written with the correct hostname, incorrect username,
correct password.
I don't see how I can return null a 2nd time after getPassword() is called
unless I "hack" it to detect if it's already been asked for.
How exactly is the repetitive call to getPassword() related to the timeout
when JSch is creating the connection socket, and is this somehow overriding
the timeout imposed on it?
On Fri, Apr 23, 2010 at 11:34 AM, Atsuhiko Yamanaka <y...@jcraft.com> wrote:
> Hi,
>
> +-From: Mick McLaughlin <mclaughlin.m...@gmail.com> --
> |_Date: Fri, 23 Apr 2010 11:20:33 -0400 ______________
> |
> |well actually no its not being invoked infinitely, however it is invoked
> |approx 35-40 times. FYI, in the testcase, the pass is correct but the
> user
> |is not...
>
> What do you mean 'the pass is correct but the user is not...'?
> Anyway, how about returning null in the second time?
>
>
> 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/
>
------------------------------------------------------------------------------
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
