Bug 202

Summary:	scp/ssh hangs
Product:	Portable OpenSSH	Reporter:	Zhe Yang <zheyang>
Component:	scp	Assignee:	OpenSSH Bugzilla mailing list <openssh-bugs>
Status:	CLOSED WORKSFORME
Severity:	major	CC:	haldane, zheyang
Priority:	P2
Version:	-current
Hardware:	ix86
OS:	All

Description Zhe Yang 2002-04-03 13:14:58 AEST

The program "scp" hangs invariably on large files (mine is 18M in length). This
behavior is observed with SSH version 3.1p1 under both Windows XP platform and
Linux [OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f].  

The sshd server is running on SunOS 5.8 (solaris).  I don't know its version,
but the accompanying ssh program shows 
"SSH version 1.2.32 [sparc-sun-solaris2.7], protocol version 1.5".  

I think that streaming under "ssh" doesn't work either: for example,
X-connection hangs up after a while (Xfree86 on Windows).

Adding "-oProtocol=1" makes everything work.

I tried OpenSSH 3.0.2p1 on Windows 2000 professional with the same sshd server
and copying large file causes no hanging problem.

This bug seems to be related to bug #124, reported by John Brown for the AIX
platform.

Zhe

Comment 1 Kevin Steves 2002-04-05 19:41:46 AEST

this only occurs with protocol 2 to the sun?
what protocol 2 server is on the sun?
ssh.com something?  i don't think they do scp over ssh2.

Comment 2 Zhe Yang 2002-04-08 12:46:04 AEST

I need to ask the system administrator here to find out which ssh server is
running on the Solaris (is there simple way to find out?)  But should an ssh
client be able to find out what protocols the ssh server supports?  

It might be a bug of the ssh server: other people using the openSSH 3.1p1
doesn't seem to suffer from this problem.

Comment 3 Ben Lindstrom 2002-04-08 12:58:25 AEST

$ telnet localhost 22
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
SSH-2.0-OpenSSH_3.1-bal

That is the best way of verifying what the server is.

- Ben

Comment 4 Zhe Yang 2002-04-08 13:19:11 AEST

Thanks, Ben.  It shows the server to be 
SSH-1.99-2.0.13 (non-commercial)

Is this a protocol 1 ssh server, then?

Comment 5 Darren Tucker 2002-08-16 10:21:46 AEST

The "1.99" means the server can do protocol 1 and 2.

Do you have a firewall, packet filter or NAT device on the path between client 
and server?

Comment 6 Duncan Haldane 2002-09-13 17:56:32 AEST

AARGH!  This bug has got me too...
Its present in the scp client of openssh-3.1p1,  but NOT in openssh-3.0p1.

The server is an old version  sshd2 of ssh-2.0.13  (from SSH Inc.), 
              SSH-1.99-2.0.13 (non-commercial)
but for various reasons the server can't be upgraded at present  :-(
so I'll have to downgarde my client to  openssh-3.0p1 to access that server.

File transfers FROM the server fail, but transfers TO the server work fine.
Its a change that occurred going from 3.0p1 to 3.1p1, so (?)
it might be easy to identify.

The bug (?) is still there in openssh-3.4p1
Its present in both the Windows client (Cygwin) and on Linux.    However the same
problem seems to afflict the latest SSH inc "noncommercial use" windows client,
so maybe  some "more correct" implementation of the protocol has exposed a
bug in the old implementations.

The file transfer almost gets completed, but hangs at the very end, a few 10's of  KB
before the end.    Only very short files get through.  (below say 30KB).

If someone gives me a clue where to start, I could hack the client with printf's to
maybe see whats going on and find out whats hanging.

This is a very annoying problem for me, as I've come
to rely on scp file transfers of work-in-progress from that server,


Duncan Haldane
<haldane@princeton.edu>

September 13, 2002.

Comment 7 Damien Miller 2003-01-07 17:49:45 AEDT

Is anyone seeing this with 3.5p1? If so, please report the software and versions
of client and server.

Comment 8 Darren Tucker 2003-05-04 22:45:57 AEST

No reports for over 6 months, closing.

Comment 9 Damien Miller 2004-04-14 12:24:18 AEST

Mass change of RESOLVED bugs to CLOSED