What steps will reproduce the problem?
1. Connect to a host that requires public key authentication and doesn't accept
any other
authebtication method.
2. If you do not have the proper private key on the phone, connectbot will
endlessly try to
connect without the key thus receiving always the same output.
What is the expected output? What do you see instead?
Connectbot behaves well, as it doesn't get stuck and you can interrupt the
attempts by
choosing disconnect from the menu. However, imho, it would be more useful to
stop it
after one, or if you feel that this failure may be due to a wrong server
answer, a couple of
attempts.
What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
1.5.5 2009.9.6
What type of system are you trying to connect to?
GNU/Linux 32bit
If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?
Please provide any additional information below.
It's not really a problem since as I already told you can interrupt the loop.
Original issue reported on code.google.com by annalisa...@gmail.com on 29 Oct 2009 at 7:36
Original issue reported on code.google.com by
annalisa...@gmail.com
on 29 Oct 2009 at 7:36