From: Jason T Hardy (jthardy@uta.edu)
Date: Tue Jul 09 2002 - 17:14:25 EDT
Thanks to Kresimir Kudumija for responding.
It turns out that OpenSSH does not like extended messages from the
remote end. This was not a problem with Tru64.
See: http://www.openssh.com/faq.html#2.9 for a description of the
problem.
In essence, Tru64 was returning a message about my password about to
expire. The sftp client didn't know what to do with that message and
aborted. You can verify if your shell is doing this by executing:
ssh yourhost /usr/bin/true
If the above command produces any output, then you need to modify your
shell initialization.
On Tue, 2002-07-02 at 11:38, Jason T Hardy wrote:
> Fellow managers,
>
> I'm having troubles starting the sftp-server on a DU 4.0d system after
> upgrading OpenSSH from 3.1p1 to 3.4p1. This issue is not repeatable on
> my Tru64 5.1 boxes. Has anyone seen this? I will summarize.
>
> Background:
> uname -m = alpha
> uname -r = V4.0
> uname -s = OSF1
> uname -v = 878
>
> OpenSSH 3.4p1 compiled with --with-ipv4-default --with-tcp-wrappers
> The sshd_config file contains: UsePrivilegeSeparation no
> The ssh daemon runs smoothly.
>
> Problem:
> <REMOTEHOST>$ sftp <HOST>
> Connecting to <HOST>...
> Received message too long 173633397
> <REMOTEHOST>$
>
> auth.log
> Jul 2 11:23:19 <HOST> sshd[7655]: Accepted publickey for <USER> from
> <REMOTEHOST_IP> port 35209 ssh2
> Jul 2 11:23:19 <HOST> sshd[7655]: subsystem request for sftp
>
> --
>
> Jason T. Hardy
> Unix Systems Administrator
> Office of Information Technology
> University of Texas at Arlington.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:46 EDT