[Your host doesn't support 'password' or 'keyboard-interactive' authentication.]

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install http://connectbot.googlecode.com/files/ConnectBot-svn-r80.apk
2. Attempt to connect to bbs@bbs.eschwa.com
3. Accept RSA fingerprint fb:4e:21:9e:45:e8:fb:d8:9e:d3:1f:c3:57:d5:f5:71

What is the expected output? What do you see instead?
Expected output: BBS splash screen / logo and login prompt.
What I see: 
Trying to authenticate
[Your host doesn't support 'password' or 'keyboard-interactive'
authentication.]
Trying to authenticate
[Your host doesn't support 'password' or 'keyboard-interactive'
authentication.]
Trying to authenticate
[Your host doesn't support 'password' or 'keyboard-interactive'
authentication.]
Trying to authenticate
[Your host doesn't support 'password' or 'keyboard-interactive'
authentication.]
Trying to authenticate
[Your host doesn't support 'password' or 'keyboard-interactive'
authentication.]

(and so forth) 

What version of the product are you using? On what operating system?
SVN r80 from link above.
T-Mobile G1; firmware 1.0

Please provide any additional information below.

Original issue reported on code.google.com by einstein...@gmail.com on 27 Oct 2008 at 3:58

[GoogleCodeExporter]

Connectbot does not yet support sshkeys.  This is supposed to be added in the 
near
future.

A quick solution is to have your ssh server support password authorization.  A 
better
solution is to wait until it's added, which should be very very soon.

W

Original comment by vva...@gmail.com on 27 Oct 2008 at 6:46

[GoogleCodeExporter]

I don't know what you're talking about. There is no "sshkeys" feature in use 
here. 

The ssh server "bbs.eschwa.com" does not require a password for the SSH 
connection.
User authentication is done by the application. 

Original comment by einstein...@gmail.com on 27 Oct 2008 at 6:55

[GoogleCodeExporter]

It looks like this host uses "none" authentication type.. e.g., no password
authentication. This should be easy enough to fix.

Original comment by kenny@the-b.org on 27 Oct 2008 at 7:28

• Changed state: Started
• Added labels: Component-Logic, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I didn't even know there was a "none" authentication type.

W

Original comment by vva...@gmail.com on 27 Oct 2008 at 7:46

[GoogleCodeExporter]

This should be fixed in SVN r83. I noticed this host closes SSH channels without
closing the connection, but that's a different issue.

Original comment by kenny@the-b.org on 27 Oct 2008 at 8:08

• Changed state: Fixed

[GoogleCodeExporter]

thanks, I can connect now!

Original comment by einstein...@gmail.com on 27 Oct 2008 at 9:30

[GoogleCodeExporter]

I'm getting this same error trying to connect with a ssh key (which is quite 
obviously supported now).  Any ideas?  The server is a router running Tomato 
Firmware v1.28.7497.
Thank you!
Billy

Original comment by jeepfr...@gmail.com on 29 Apr 2012 at 5:53

[GoogleCodeExporter]

Woot!  Never mind!  I just had to edit the connection and select the ssh key I 
wanted to be used.  Sorry for the distraction!  Thanks for the great app!
Billy

Original comment by jeepfr...@gmail.com on 29 Apr 2012 at 5:55

[GoogleCodeExporter]

I'm experiencing this problem with ConnectBot 1.7.1 on Galaxy i9000 on two SSH 
conections. There is no password and the sole SSH public key is on the 
authorised keys list of the SSH servers. 

Only ConnectBot has a problem connecting - other machines connect without 
problems. The port is obfuscated ie not 22 and the servers are running a recent 
version of dd-wrt. 

Original comment by johnr67...@gmail.com on 24 Jun 2012 at 5:46