Wait for SSH server to send banner before sending our banner

[GoogleCodeExporter]

I love ConnectBot, but I miss the ability to change advanced SSH. I would 
especially need connetion timeout configuration.

Keep up the good work guys!

Original issue reported on code.google.com by dlux@dlux.cc on 13 Aug 2009 at 10:09

[GoogleCodeExporter]

I'm not sure what you're requesting. Could you explain what the issue is? 
Connection
timeout when trying to establish a TCP session? Is there an analogous setting in
another SSH client perhaps?

Original comment by kenny@the-b.org on 14 Aug 2009 at 2:53

[GoogleCodeExporter]

Hey,

Sorry for the loose phrasing. Actually what I need is that the client should 
wait for a 
long time for the SSH "hello" string from the server.

But looking at the code (http://www.google.com/codesearch/p?
hl=en&sa=N&cd=5&ct=rc#x3OoZRNv-
Ek/trunk/connectbot/src/com/trilead/ssh2/transport/ClientServerHello.java&q=SSH
-%20package:http://connectbot%5C.googlecode%5C.com), it seems that the client 
initiates the connection with the SSH-2.0-<connection_id> string, instead of 
waiting 
for the server to print its "SSH-version-..." string.

Openssh client first waits for the server handshake header, and then send the 
client 
handskake header.

I have a special configuration in my server side, which REQUIRES that the 
client waits 
for the server to print the header after the TCP connection established...

I did not find it in the standard (I did not look it too deeply, though), maybe 
this is an 
acceptable behaviour...

Original comment by dlux@dlux.cc on 14 Aug 2009 at 4:32

[GoogleCodeExporter]

Hi,

Ok, I've found what I've looked for:

http://www.networksorcery.com/enp/rfc/rfc4253.txt

The standard does not say that the server or client should send the header 
first, so 
actually there is no bug in the code, my assumption was wrong when I assumed 
that 
the server sends the header first always.

I would change the ClientServerHello function in ClientServerHello.java to send 
the 
SSH string after the lines are arrived from the server. What do you think about 
that?

Original comment by dlux@dlux.cc on 14 Aug 2009 at 4:48

[GoogleCodeExporter]

The change your suggesting would slow down the initial negotiation especially 
since
we're normally doing this over potentially high latency mobile networks.

Original comment by kenny@the-b.org on 14 Aug 2009 at 9:36

[GoogleCodeExporter]

Original comment by kenny@the-b.org on 14 Aug 2009 at 11:25

• Changed title: Wait for SSH server to send banner before sending our banner
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Yes, indeed it would slow down the connection, so I imagine an option somewhere 
hidden behind some "advanced" menu of per-connection settings, and by default, 
it 
should be turned off.

Original comment by dlux@dlux.cc on 17 Aug 2009 at 3:12

[GoogleCodeExporter]

Please, any chance that this magic option will be added? 

some software (sslh) use this trick to allow multiple protocols on one port,
especially on port 443, to bypass stupid proxies...

Original comment by n.legail...@gmail.com on 24 Mar 2010 at 9:52

[GoogleCodeExporter]

Hello, I second this request to allow sslh to work!

Original comment by victor.n...@gmail.com on 27 Mar 2010 at 12:48

[GoogleCodeExporter]

I also use sslh, so any ability to modify advanced connection initialization 
per session may be a good point to me. Thanks for this neat tool.

Original comment by jcarnu on 29 Sep 2011 at 6:57

[GoogleCodeExporter]

Also interested. I'd love to be able to use connectbot. But without this 
feature, it's useless if you use sslh on your server.

Original comment by sylvain....@gmail.com on 5 Sep 2012 at 12:16

[GoogleCodeExporter]

I would like to put another vote for sslh port multiplexer in order to make 
connectbot useable on port 443!

Original comment by familie....@gmail.com on 13 Mar 2015 at 7:30