[Info-vax] Potential loss of data problem in sftp client in TCP/IP Services ?

[VAXman- at SendSpamHere.ORG]

In article <00ABE4A1.4475A1A0 at SendSpamHere.ORG>, VAXman-  @SendSpamHere.ORG writes:
>In article <jjnc5c$1l5$1 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>On 2012-03-13, VAXman-  @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
>>> In article <jjn54r$vek$1 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>>>On 2012-03-12, David Froble <davef at tsoft-inc.com> wrote:
>>>>>
>>>>> I'm still trying to understand the problem.  You indicate that you had been using V5.6 
>>>>> ECO5.  Are you saying the problem exists in this version?
>>>>>
>>>>
>>>>No, the file truncation problem does not exist in the sftp image supplied
>>>>with ECO5, but other different problems do exist, which is why the latest
>>>>Engineering images were loaded onto the system in question.
>>>>
>>>>This file truncation problem is clearly a very recent problem. I am still
>>>>waiting to hear back from HP, so in the meantime I am trying to find out
>>>>if anyone else can duplicate this using the most recent TCP/IP ECO (V5.7
>>>>ECO3).
>>>
>>> I just transferred my LOGIN.COM file to one of my Ubuntu laptops:
>>>
>>
>>Thanks for doing this. Just for confirmation, was this V5.7, ECO3 ?
>
>Yes.
>
>
>>> $ sftp -oPort=###### vaxman at 192.168.#.###
>>>   
>>> sftp> cd Desktop
>>> /home/vaxman/Desktop
>>> sftp> put login.com
>>>  login.com (src): got EOF reading file (server msg: 'Encountered EOF.')
>>> sftp> 
>>>
>>> On the Ubuntu Laptop, 'gedit' opened the file just fine and all of its
>>> contents were available.  If you can give me a couple of "reproducers"
>>> which exhibit your issue, I'll give them a try.
>>>
>>> I've been using 'sftp' extensively to transfer files to and from my VMS
>>> systems to my Linux systems and I've never seen any problems exhibited.
>>> I'm not saying there aren't any issues, just that my files just haven't
>>> exhibited problems that yours have.
>>>
>>
>>I've just created a simple file which reproduces the problem for me:
>>
>>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>>BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
>>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
>>DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
>>EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
>>FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
>>GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG
>>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
>>IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
>>JJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJ
>>KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
>>LLLLLLLLLLLLLLLLLLLLLLLL
>>MMMMM
>>
>>When transferred to a Linux sftp server, this is what is received:
>>
>>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>>BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
>>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
>>DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
>>EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
>>FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
>>GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG
>>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
>>IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
>>JJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJ
>>KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
>>LLLLLLLLLLLLLLLLLL
>>
>>Note the M's and the last few L's are missing.
>
>$ CREATE SIMON.TEST
>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB                               
>CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
>DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
>EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
>FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
>GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG
>HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
>IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
>JJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJJ
>KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
>LLLLLLLLLLLLLLLLLLLLLLLL
>MMMMM[ Exit ]
>$ sftp -oPort=###### vaxman at 192.168.#.###
>sftp> put simon.test
>
>I see everything when I open the file with 'gedit'.

FWIW, I tried this:

$ CONVERT/FDL="Record; Format VFC" SYS$INPUT SIMON.TEST

And supplied the same data as before.  It would appear that the sftp client
on VMS does not handle the VFC and sends it to the remote.  'gedit' will not
open it; more simon.test returns blank lines; and WINE NotePad will display
all of the contents.  'sftp' is not reading the VFC file's VFC; it's simply
sending it to the remote as data.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.