nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-05-30 00:04:49 -05:00
Code Issues Projects Releases Wiki Activity

Improve documentation of the SCP wildcard safety issue: in

Browse Source 
particular, mention that doing an SCP wildcard download into a clean
directory is adequate protection against a malicious server trying
to overwrite your files.

[originally from svn r5279]
This commit is contained in:
Simon Tatham 2005-02-09 15:57:07 +00:00
parent 4ae1aa3b48
commit 2f7de95a2e
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/pscp.but
View File

@ -96,10 +96,10 @@ direction, like this:
However, in the second case (using a wildcard for multiple remote However, in the second case (using a wildcard for multiple remote
files) you may see a warning saying something like \q{warning: files) you may see a warning saying something like \q{warning:
remote host tried to write to a file called 'terminal.c' when we remote host tried to write to a file called \cq{terminal.c} when we
requested a file called '*.c'. If this is a wildcard, consider requested a file called \cq{*.c}. If this is a wildcard, consider
upgrading to SSH 2 or using the '-unsafe' option. Renaming of this upgrading to SSH 2 or using the \cq{-unsafe} option. Renaming of
file has been disallowed}. this file has been disallowed}.
This is due to a fundamental insecurity in the old-style SCP This is due to a fundamental insecurity in the old-style SCP
protocol: the client sends the wildcard string (\c{*.c}) to the protocol: the client sends the wildcard string (\c{*.c}) to the
@ -128,7 +128,11 @@ happen. However, you should be aware that by using this option you
are giving the server the ability to write to \e{any} file in the are giving the server the ability to write to \e{any} file in the
target directory, so you should only use this option if you trust target directory, so you should only use this option if you trust
the server administrator not to be malicious (and not to let the the server administrator not to be malicious (and not to let the
server machine be cracked by malicious people). server machine be cracked by malicious people). Alternatively, do
any such download in a newly created empty directory. (Even in
\q{unsafe} mode, PSCP will still protect you against the server
trying to get out of that directory using pathnames including
\cq{..}.)
\S2{pscp-usage-basics-user} \c{user} \S2{pscp-usage-basics-user} \c{user}