Need to add "keyboard-interactive" authentication method about connectbot HOT 18 CLOSED

Any ETA on this?  All of my machines are FreeBSD based.

I can press enter and receive a password prompt but password is never accepted. 
Also
running FreeBSD system.

I just downloaded and tried it and I get: 

The authenticity of host 'io.com' can't be established.

Trying to authenticate

and then hangs.  (You can try it yourself: the location is io.com:22)

Thanks.

More details.  When I use putty, I get:

login as: [my-own-user-name]
Using keyboard-interactive authentication.
Password: 
Last login: Wed Oct 22 16:38:20 2008 from 12.31.188.98
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
        The Regents of the University of California.  All rights reserved.

FreeBSD 6.3-STABLE (GENERIC) #2: Sat Feb 16 18:48:27 CST 2008

I get the same error running a Linux box. It looks like it's hanging waiting 
for a
response from the server. If I type in my password, it tells me authentication
failed, then gives me a 'Password:' prompt, but it never accepts the password I 
give,
nor does my server leave any trace that I tried to connect.

It looks like the server is only accepting "keyboard-interactive" and not 
"password"
 You can verify this by using "ssh -v [hostname]" with OpenSSH. As a work-around, you
can enable "PasswordAuthentication yes" (on OpenSSH; others will have something
similar) for now until this is fixed.

Is there any idea on when this will be fixed?

I was having an issue entering my password, but I figured out that typing 
uppercase 
letters works differently in the terminal than in other Android apps. You have 
to 
hold down alt or shift and press the button simultaneously like you are using a 
computer keyboard in order to type symbols and uppercase letters. Anyone who is 
experiencing this issue should be aware of this quirk, it might actually be 
causing 
you to type a case-sensitive password in all lowercase.

At org/connectbot/service/TerminalBridge.java:161 there needs to be some error 
that
pops up if no authentication methods are possible.

Jeffrey, could you put something that lets the user know that authentication 
wasn't
possible and terminates the connection? Listing out the possible authentication 
types
for the client and the server would be good in this error message.

Okay, I added keyboard-interactive in r76. Could some people test it on their 
devices
and report how it works?

Works great for me. Thanks!

Woo! Works for me.

Actually, I might have a problem. If I type "exit" to logout, it tells me 
logout and
just sits there. It looks like I can't even disconnect from the menu now, and 
it just
sits there sorta hung. Since it never recognizes the disconnect, I'm not able to
connect again.

Correction, I can disconnect from the session, but not from the main menu. So I 
guess
it's unrelated to keyboard-interactive.

Works for me, thank you!

Ouch.  The fact that this app breaks the UI (SHIFT and ALT work differently) is
EVIL... it needs to be in big neon letters somewhere.  If I hadn't stumbled 
across
this entry by accident, I'd still be trying to enter my password.

lol be careful with your "evil" label--it probably just isnt fixed yet.

however, are you using the latest svn that has a password textfield at the 
bottom of
the window?  we switched to using that for just this reason--it should 
automagically
behave just like any other password prompt on android.

keyboard-interactive is working awesome!  thx kenny  :)