12-11-2018, 02:32 PM
Reply to comments to date:1) of course not. Only the output and debug data of the sending host is shown and only the target host IP appears in that output. As indicated, IP addresses have been obscured for security reasons.
2) The '-t' option doesn't appear in the scp man page and was not supplied on the command lines shown. The use of '-t' is entirely internal to the scp file transfer protocol.
3) Again, the exact same send command works fine on other ssh server installations and used to work on earlier Lite releases. Everything shown in the debug log is reflective of the internal scp protocol and not intended or implied by my command ('scp -prvv SourceDir hostip:destdir' [the 'p' option preserves file dates and modes, the 'r' option indicates recursive copy of everything in the source directory including any sub-directory structure, the double 'v' is level 2 debug used only because it isn't working]). This is a very powerful tool I would like to continue to use but now it's broke.
4) Both workstations are laptops and the ssh protocols are being used to transfer files between them. Very common practice that I use all the time. That is why I discovered it was broken in this latest Lite release.
5) I do too as I said. Apparently only the Linux Lite4.2 ssh package is broken for both scp and sftp to the Lite4.2 ssh server. The ssh server side (sshd) is not included in the Lite4.2 install ISO. It had to be installed manually using the Synaptic Package Manager as indicated at the beginning of the post (the SPM automatically takes care of all necessary dependencies). After that, the Lite4 firewall had to be configured to allow incoming connections. The Lite4.2 server (sshd) works for ssh logins but not either scp or sftp. If it's not broken then why doesn't it work? As I said, it used to work fine and I depend on it to keep a number of workstations current.
2) The '-t' option doesn't appear in the scp man page and was not supplied on the command lines shown. The use of '-t' is entirely internal to the scp file transfer protocol.
3) Again, the exact same send command works fine on other ssh server installations and used to work on earlier Lite releases. Everything shown in the debug log is reflective of the internal scp protocol and not intended or implied by my command ('scp -prvv SourceDir hostip:destdir' [the 'p' option preserves file dates and modes, the 'r' option indicates recursive copy of everything in the source directory including any sub-directory structure, the double 'v' is level 2 debug used only because it isn't working]). This is a very powerful tool I would like to continue to use but now it's broke.
4) Both workstations are laptops and the ssh protocols are being used to transfer files between them. Very common practice that I use all the time. That is why I discovered it was broken in this latest Lite release.
5) I do too as I said. Apparently only the Linux Lite4.2 ssh package is broken for both scp and sftp to the Lite4.2 ssh server. The ssh server side (sshd) is not included in the Lite4.2 install ISO. It had to be installed manually using the Synaptic Package Manager as indicated at the beginning of the post (the SPM automatically takes care of all necessary dependencies). After that, the Lite4 firewall had to be configured to allow incoming connections. The Lite4.2 server (sshd) works for ssh logins but not either scp or sftp. If it's not broken then why doesn't it work? As I said, it used to work fine and I depend on it to keep a number of workstations current.