Home
|
FAQ
|
Feedback
|
Licence
|
Updates
|
Mirrors
|
Keys
|
Links
|
Team
Download:
Stable
·
Pre-release
·
Snapshot
|
Docs
|
Privacy
|
Changes
|
Wishlist
PSCP, when it is using the SCP protocol (which is rare), and has been configured to preserve timestamps and permissions (with -p) on a downloaded file can, due to a mistake in the protocol implementation, get the file name wrong, create a local file with an unhelpful mode, get the size wrong and perhaps hang, maybe print bits of the file content to the console, and generally makes a complete hash of things. For instance:
$ ./pscp -scp -remotehost:stoat .
Keyboard-interactive authentication prompts from server:
| Password:
End of keyboard-interactive prompts from server
warning: remote host tried to write to a file called '0 1559391040 0
0664 160166 stoat
'
when we requested a file called 'stoat'.
If this is a wildcard, consider upgrading to SSH-2 or using
the '-unsafe' option. Renaming of this file has been disallowed.
stoat | 32 kB | 32.0 kB/s | ETA: 00:04:45 | 0%
[hang]
In most circumstances, PSCP will use the more modern SFTP protocol, which does not have this problem. The SCP protocol will only be used if the server doesn't appear to support SFTP (rare), or if the user explicitly specified the -scp option on the command line.