SFTP (x86/VMS) issues
Posted: Wed Sep 27, 2023 3:14 pm
Issue #1 (cd)
On a VSI x86 VMS VM, if I do a $sftp 127.0.0.1 (loopback to the same VSI system). Once logged in:
1) cd rduser:[prince.temp]
response = realpath rduser:[prince.temp]: No such file
2) cd [.temp]
response = Can't change directory: "/DISK$B_VAXVMSV921/RDUSER/PRINCE/TEMP/[.temp]" is not a directory
3) cd temp (will work)
System Details:
VSI 9.2-1, 9.2-1X_UPDATE V1.0, OpenSSH V8.9-1F
Authorize default is "RDUSER:[PRINCE]"
RDUSER:[PRINCE.TEMP] does exist. Protection is O:RWED
Issue #2 (put)
From the VSI x86 VMS/VM, I can sftp to a HPE I64 system The "put" command will fail
put cmsrootdev.sav
response = Uploading cmsrootdev.sav to bnevad$dka0:[RDUSER.PRINCE]/cmsrootdev.sav
dest open "bnevad$dka0:[RDUSER.PRINCE]/cmsrootdev.sav": Failure
If I try and reverse the flow and log into the VSI system from the HPE system, the put will still fail, just a different error
put cmsrootdev.sav
response =
Warning: child process (/sys$system/tcpip$ssh_ssh2) exited with code 0.
%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation
Interesting part here, is the file is created on the VSI side, with the same allocation as the HPE side (368592 blocks). Just nothing in the file.
Kind of odd that "get" works in either direction, but "put" will fail in either direction between HPE IA64/VMS and VSI x86/VMS
System Details:
HPE VMS 8.4, VMS84I_UPDATE V11.0, TCP V5.7-13ECO5
VSI 9.2-1, 9.2-1X_UPDATE V1.0, OpenSSH V8.9-1F
Rod
On a VSI x86 VMS VM, if I do a $sftp 127.0.0.1 (loopback to the same VSI system). Once logged in:
1) cd rduser:[prince.temp]
response = realpath rduser:[prince.temp]: No such file
2) cd [.temp]
response = Can't change directory: "/DISK$B_VAXVMSV921/RDUSER/PRINCE/TEMP/[.temp]" is not a directory
3) cd temp (will work)
System Details:
VSI 9.2-1, 9.2-1X_UPDATE V1.0, OpenSSH V8.9-1F
Authorize default is "RDUSER:[PRINCE]"
RDUSER:[PRINCE.TEMP] does exist. Protection is O:RWED
Issue #2 (put)
From the VSI x86 VMS/VM, I can sftp to a HPE I64 system The "put" command will fail
put cmsrootdev.sav
response = Uploading cmsrootdev.sav to bnevad$dka0:[RDUSER.PRINCE]/cmsrootdev.sav
dest open "bnevad$dka0:[RDUSER.PRINCE]/cmsrootdev.sav": Failure
If I try and reverse the flow and log into the VSI system from the HPE system, the put will still fail, just a different error
put cmsrootdev.sav
response =
Warning: child process (/sys$system/tcpip$ssh_ssh2) exited with code 0.
%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation
Interesting part here, is the file is created on the VSI side, with the same allocation as the HPE side (368592 blocks). Just nothing in the file.
Kind of odd that "get" works in either direction, but "put" will fail in either direction between HPE IA64/VMS and VSI x86/VMS
System Details:
HPE VMS 8.4, VMS84I_UPDATE V11.0, TCP V5.7-13ECO5
VSI 9.2-1, 9.2-1X_UPDATE V1.0, OpenSSH V8.9-1F
Rod