stevel 2005/05/15 14:13:06
Modified: docs/manual/OptionalTasks scp.html
Log:
scp doc tweakage.
Revision Changes Path
1.19 +11 -4 ant/docs/manual/OptionalTasks/scp.html
Index: scp.html
===================================================================
RCS file: /home/cvs/ant/docs/manual/OptionalTasks/scp.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- scp.html 29 Apr 2005 18:58:09 -0000 1.18
+++ scp.html 15 May 2005 21:13:06 -0000 1.19
@@ -13,7 +13,7 @@
<p><em>since Ant 1.6</em></p>
-<p>Copies a file or FileSet to or from a remote machine running SSH daemon.
+<p>Copies a file or FileSet to or from a (remote) machine running an SSH
daemon.
FileSet <i>only</i> works for copying files from the local machine to a
remote machine.</p>
@@ -210,15 +210,22 @@
<p><strong>Security Note:</strong> Hard coding passwords and/or usernames
in scp task can be a serious security hole. Consider using variable
-substitution and include the password on the command line. For example:<br>
+substitution and include the password on the command line. For example:
+<p>
<pre>
<scp todir="${username}:[EMAIL PROTECTED]:/dir" ...>
</pre>
-Invoke ant with the following command line:
+Invoking ant with the following command line:
<pre>
ant -Dusername=me -Dpassword=mypassword target1 target2
</pre>
-</p>
+
+Is slightly better, but the username/password is exposed to all users on an
Unix
+system (via the ps command). The best approach is to use the
+<code><input></code> task and/or retrieve the password from a (secured)
+.properties file.
+
+<p>
<p><strong>Unix Note:</strong> File permissions are not retained when files
are copied; they end up with the default <code>UMASK</code> permissions
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
