On 4/13/12 7:45 PM, Peter Stuge wrote:
> Jasmeet Bagga wrote:
>> Only one thread does. However I am getting login failures with
>> error message "Failed getting banner".
> You need to provide COMPLETE details of your problem. I suggest
> enabling tracing and sending the full log to the list.
The log is attached. I did further debugging and found that ssh via open
ssh succeeds, however when I enabled verbose option on it, I see some
lines that are interesting
DUKEOSTPDZ01:/var/tmp/jasmeet#ssh -v packet-design_at_172.17.248.203
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 172.17.248.203 [172.17.248.203] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version
OpenSSH_4.4 ---> Remote version is 1.99
debug1: match: OpenSSH_4.4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
This shows that the remote protocol version is 1.99. Does libssh2 work
with that ? I would assume no, but the folks using this device claim
that it used to work and then suddenly started failing without any
change to the device.
>> it seems the problem went away after compiling with -D_REENTRANT. I
>> tried this but it didn't help. Unfortunately I can't access the
>> associated ticket as libssh2 trac is down.
> Try now. http://trac.libssh2.org/ticket/99
> libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2012-04-16