Summary: DU FTP doesn't conform to RFC

From: John Nebel <nebel_at_athena.csdco.com>
Date: Sun, 19 Jul 1998 08:30:38 -0600 (MDT)

Joerg Czeranski suggested:

If DEC doesn't have a patch for you and you consider replacing the
ftp daemon, I'd suggest using a Berkeley ftp daemon as DEC's ftpd
is derived from it. You can find the source of the 4.3BSD ftpd on
ftp.funet.fi and daemons derived from the 4.4BSD ftpd on any
FreeBSD or NetBSD mirror.

Thanks. I had wu-ftpd on another machine and that solved the problem.
We are also following up on Joerg's suggestion.

The below is an example of what is broken. I used the VMS editor to
create a file with three line feeds and then sent it to DU.

FTP> send x.lis
200 PORT command successful.
150 Opening ASCII mode data connection for x.lis (198.80.11.41,4277).
230-WARNING! 3 bare linefeeds received in ASCII mode
   File may not have transferred correctly.
226 Transfer complete.
local: SYS$SYSROOT:[SYSMGR]X.LIS;23 remote: x.lis
5 bytes sent in 00:00:00.00 seconds (0.54 Kbytes/s)

The 230 and 226 lines should have the same code. IBM MVS insists on
this. It's in the RFC. Since EBCDIC x'00' is translated to line feeds
(also in the RFC) it makes MVS >> DU ftp problematic.

Got us in big trouble Friday. At one point six people were working on
the problem on both the MVS and DU/VMS sides.

John Nebel
Received on Sun Jul 19 1998 - 16:31:35 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT