openssh unix dev - Feb 2001 - Problems with sftp under SCO OpenServer

Hello,

I compiled OpenSSH 2.5.1p1 for SCO OpenServer 5.0.5, HPUX B.11.00, and
SunOS 5.7.  When I sftp into the HP or Sun box, everything works fine.
However, whenever I sftp into the OpenServer box, all remote filenames
are shown as "(null)".  File sizes, owners, etc. display properly. 
This
behavior is exhibited from all origination points.

OpenSSH was configured with identical parameters (apart from the path to
xauth), and compiled with OpenSSL 0.9.6 and zlib-1.1.3 under all
systems.


Thanks,
Greg Jewell

On Thu, 22 Feb 2001, Greg Jewell wrote:
> Hello,
> 
> I compiled OpenSSH 2.5.1p1 for SCO OpenServer 5.0.5, HPUX B.11.00, and
> SunOS 5.7.  When I sftp into the HP or Sun box, everything works fine.
> However, whenever I sftp into the OpenServer box, all remote filenames
> are shown as "(null)".  File sizes, owners, etc. display
properly.  This
> behavior is exhibited from all origination points.
> 
Which compiler are you using under OpenServer?

- Ben

On Thu, 22 Feb 2001, Greg Jewell wrote:
> Hello,
> 
> I compiled OpenSSH 2.5.1p1 for SCO OpenServer 5.0.5, HPUX B.11.00, and
> SunOS 5.7.  When I sftp into the HP or Sun box, everything works fine.
> However, whenever I sftp into the OpenServer box, all remote filenames
> are shown as "(null)".  File sizes, owners, etc. display
properly.  This
> behavior is exhibited from all origination points.
I have verified this problem with 2.5.1p2 and 03/10 CVS.
...
debug2: Remote version: 3
debug3: Sent message fd 6 T:16 I:1
debug3: SSH_FXP_REALPATH . -> /tmp_mnt/homes/tim
sftp> dir xx
debug3: Sent message fd 6 T:16 I:2
debug3: SSH_FXP_REALPATH /tmp_mnt/homes/tim/xx -> /tmp_mnt/homes/tim/xx
debug3: Sent message fd 6 T:17 I:3
debug3: Received stat reply T:105 I:3
debug3: Sending SSH2_FXP_READDIR I:5
debug3: Received reply T:104 I:5
debug3: Received 6 SSH2_FXP_NAME responses
drwxrwxr-x    6 tim      trr          4096 (null) Aug 23  2000
drwxr-xr-x   23 tim      trr          4096 (null) Mar 10 19:44
drwxrwxr-x    2 tim      trr          4096 (null) May 10  2000
drwxrwxr-x    2 tim      trr          4096 (null) Sep 17 10:42
drwxrwxr-x    2 tim      trr          4096 (null) Jun 22  2000
drwxrwxr-x    4 tim      trr          4096 (null) Aug 28  2000
debug3: Sending SSH2_FXP_READDIR I:6
debug3: Received reply T:101 I:6
debug3: Received SSH2_FXP_STATUS 1
debug3: Sent message SSH2_FXP_CLOSE I:7
debug3: SSH2_FXP_STATUS 0
sftp> 
...

The server side debuging seems to be non existant.

I've looked at the sftp-server code and I am stumped.
Again, the problem only shows up on Open Server 5 sftp-server

Any clues how to track this down?
> 
> OpenSSH was configured with identical parameters (apart from the path to
> xauth), and compiled with OpenSSL 0.9.6 and zlib-1.1.3 under all
> systems.
> 
> 
> Thanks,
> Greg Jewell
> 
> 
-- 
Tim Rice				Multitalents	(707) 887-1469
tim at multitalents.net

On Sat, 10 Mar 2001, Tim Rice wrote:
> On Thu, 22 Feb 2001, Greg Jewell wrote:
> 
> > Hello,
> > 
> > I compiled OpenSSH 2.5.1p1 for SCO OpenServer 5.0.5, HPUX B.11.00, and
> > SunOS 5.7.  When I sftp into the HP or Sun box, everything works fine.
> > However, whenever I sftp into the OpenServer box, all remote filenames
> > are shown as "(null)".  File sizes, owners, etc. display
properly.  This
> > behavior is exhibited from all origination points.
> 
> I have verified this problem with 2.5.1p2 and 03/10 CVS.
> ...
> debug2: Remote version: 3
> debug3: Sent message fd 6 T:16 I:1
> debug3: SSH_FXP_REALPATH . -> /tmp_mnt/homes/tim
> sftp> dir xx
> debug3: Sent message fd 6 T:16 I:2
> debug3: SSH_FXP_REALPATH /tmp_mnt/homes/tim/xx -> /tmp_mnt/homes/tim/xx
> debug3: Sent message fd 6 T:17 I:3
> debug3: Received stat reply T:105 I:3
> debug3: Sending SSH2_FXP_READDIR I:5
> debug3: Received reply T:104 I:5
> debug3: Received 6 SSH2_FXP_NAME responses
> drwxrwxr-x    6 tim      trr          4096 (null) Aug 23  2000
> drwxr-xr-x   23 tim      trr          4096 (null) Mar 10 19:44
> drwxrwxr-x    2 tim      trr          4096 (null) May 10  2000
> drwxrwxr-x    2 tim      trr          4096 (null) Sep 17 10:42
> drwxrwxr-x    2 tim      trr          4096 (null) Jun 22  2000
> drwxrwxr-x    4 tim      trr          4096 (null) Aug 28  2000
There was an off list talk about this.  Since SCO native snprintf()
does not support %ll concept it does things incorrectly.  However the
new 64bit development does support %ll.

The best way to deal with this is to test to see if the
snprintf() supports %ll and define BROKEN_SNPRINTF if it does
not.

- Ben