Comment 1 Malgorzata Janczarska 2011-06-14 12:28:21 EDT

Tomek, do you think it's doable in RC2?

Comment 2 Tomasz Zarna 2011-06-15 06:08:41 EDT

Since failing to authenticate when setting up a JSch session[1] will always 'throw new JSchException("Auth fail");' no matter which auth method has been used, I guess the best approach would be to provide our own implementation of UserInfo[2]. However, I don't think this is something I will be able to do for RC2.

[1] com.jcraft.jsch.Session.connect(int)
[2] com.jcraft.jsch.UserInfo

Comment 3 Tomasz Zarna 2011-07-12 12:12:33 EDT

(In reply to comment #2)
> failing to authenticate when setting up a JSch session[1] will always
> 'throw new JSchException("Auth fail");' 

This seems to be a known issue in JSCh, here is a feature request for making the exception messages more informative - http://sourceforge.net/tracker/?func=detail&aid=1047646&group_id=64920&atid=509125. Since we don't know which auth method actually failed and for what reason, having an implementation of UserInfo won't help us much. This means that the request may be considered as blocking this bug.

Comment 4 Szymon Brandys 2011-09-12 04:33:21 EDT

Looks like we need to reset the target milestone for this bug then. Tomek, could you put pressure on JSch guys and find out when they are fixing it?

Comment 5 Tomasz Zarna 2011-09-12 08:16:12 EDT

I'm afraid you're right. Unless someone from JSch fixes the request quickly and we consume it right away there is very little chance for having this fixed for 0.3.

I've commented on the JSch issue tracker and posted on their mailing list. Will update the bug as soon as I get any response.

Comment 6 John Arthorne 2015-05-05 14:54:23 EDT

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html