commandline » Revisions »
Differences
This shows you the differences between the selected revisions of the page.
2020-12-02 | 2020-12-02 | ||
grammar (martin) | 5.18 Bug 1821: Alternative way to provide credentials in scripting/command-line without URL-encoding (martin) | ||
Line 14: | Line 14: | ||
winscp.exe [mysession] /refresh [path] | winscp.exe [mysession] /refresh [path] | ||
winscp.exe [mysession] /upload file1 file2 file3 ... [/defaults[=secs]] | winscp.exe [mysession] /upload file1 file2 file3 ... [/defaults[=secs]] | ||
+ | winscp.exe [mysession] [/username=<user>] [/password=<pass>] | ||
winscp.exe [mysession] [/privatekey=<file> [/passphrase=<passphrase>]] | winscp.exe [mysession] [/privatekey=<file> [/passphrase=<passphrase>]] | ||
winscp.exe [mysession] [/hostkey=<fingerprint>] | winscp.exe [mysession] [/hostkey=<fingerprint>] | ||
Line 55: | Line 56: | ||
If there's already idle WinSCP instance running, the session(s) opens in the existing instance. To force session open in new instance of WinSCP, use ''/==newinstance=='' parameter. | If there's already idle WinSCP instance running, the session(s) opens in the existing instance. To force session open in new instance of WinSCP, use ''/==newinstance=='' parameter. | ||
+ | |||
+ | You can use the parameters ''/username'' and ''/password'' as an alternative way to specify the credentials. The credentials are normally part of the [[session_url|session URL]]. Using these switches has the advantage of not needing to [[session_url#special|URL-encode special characters]]. &beta_feature | ||
The parameter ''/privatekey'' specifies a [[local_path|local path]] to an [[public_key#private|SSH private key file]]. If the key file is encrypted, use the ''/passphrase'' to specify its passphrase. | The parameter ''/privatekey'' specifies a [[local_path|local path]] to an [[public_key#private|SSH private key file]]. If the key file is encrypted, use the ''/passphrase'' to specify its passphrase. |