Parameters for winscp.exe executable:winscp.exe site|workspace|folder winscp.exe <session_url>[/path/[file]] winscp.exe [mysession] [/sessionname=<name>] winscp.exe [mysession] [/newinstance] winscp.exe [mysession] /edit <path> winscp.exe [mysession] /synchronize [local_directory] [remote_directory] [/defaults] winscp.exe [mysession] /keepuptodate [local_directory] [remote_directory] [/defaults] winscp.exe [mysession] /refresh [path] winscp.exe [mysession] /upload file1 file2 file3 ... [/defaults] winscp.exe [mysession] [/privatekey=<file>] [/hostkey=<fingerprint>] winscp.exe [mysession] [/clientcert=<file>] [/certificate=<fingerprint>] winscp.exe [mysession] [/passive[=on|off]] [/implicit|explicit] winscp.exe [mysession] [/timeout=<sec>] winscp.exe [mysession] [/rawsettings setting1=value1 setting2=value2 ...] winscp.exe [/console] [/script=script_file] [/command command1 command2 ...] [/parameter // param1 ...] winscp.exe [/log=<logfile> [/loglevel=<level>] [/logsize=[count*]<size>]] [/xmllog=<logfile> [/xmlgroups]] winscp.exe [/ini=<inifile>] winscp.exe [/rawconfig config1=value1 config2=value2 ...] winscp.exe /batchsettings <site_mask> setting1=value1 setting2=value2 ... winscp.exe /Crack keyfile [/output=output] [/changepassphrase] [/comment=comment] winscp.exe /update winscp.exe /help
Parameters for winscp.com executable:winscp.com [/script=script_file] [/command command1 command2 ...] [/parameter // param1 ...] winscp.com [/log=<logfile> [/loglevel=<level>] [/logsize=[count*]<size>]] [/xmllog=<logfile> [/xmlgroups]] [/nointeractiveinput] winscp.com [/ini=<inifile>] winscp.com [/rawconfig config1=value1 config2=value2 ...] winscp.com /batchsettings <site_mask> setting1=value1 setting2=value2 ... winscp.com /Patch keyfile [/output=output] [/changepassphrase] [/comment=comment] winscp.com /help Session
The first syntax opens the site. To open site, stored in folder, use path syntax “folder/site”. You can also open workspace or all sites in site folder.
The second creates the session specified by session URL and optionally by initial remote path. If the remote path is not ended by slash (/), it is treated as path to file (or even directory) that should be downloaded.
Parameter /sessionname specifies a custom name of the session to be used instead of the automatically generated name in a format username@hostname or to override the name of the saved site.
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.
Parameter /privatekey specifies local path to SSH private key file.
Parameter /hostkey specifies fingerprint of expected SSH host key (or several alternative fingerprints separated by semicolon). It makes WinSCP automatically accept host key with the fingerprint.
Parameter /clientcert specifies local path to FTPS or WebDAVS TLS/SSL client certificate.
When the FTPS or WebDAVS Portable TLS/SSL certificate is not trusted (typically a self-signed certificate), use parameter /certificate to specify a fingerprint of the untrusted certificate. It makes WinSCP trust the certificate. Several alternative fingerprints can be separated by semicolon.
Parameter /passive enables passive (=on) or Passive (=off) transfer mode (FTP protocol only).
Parameters /implicit, and /explicit enable respective method of invoking FTPS.
Parameter /timeout specifies Portable response timeout.
Parameter /rawsettings allows configuring any site settings using raw format as in an INI file. E.g. to enable SSH compression and agent forwarding use /rawsettings Compression=1 AgentFwd=1. The parameter must come after session URL (if any).
When using scripting, use open command (and its switches) instead.winscp.exe "My site" winscp.exe SSH Transfer of File Protocol://martin:email@example.com/ /hostkey="ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx..." winscp.exe scp://firstname.lastname@example.org:2222/ /privatekey=mykey.ppk winscp.exe ftps://martin:email@example.com/ Logging
With /log parameter you may turn on session logging to file specified by local path.
Use parameter /loglevel to change logging level. The value can be in range 0..2 (for Normal, Debug 1 and Debug 2 logging levels respectively). Append additional * to enable password logging (e.g. /loglevel=2*).1
Use parameter /logsize to configure log file size limit and log file rotation. Specify maximum size in bytes, optionally with K, M or G units. Optionally you can limit number of archived log files using count* prefix. For example /logsize=5*10M will limit log file size to 10 MB and will allow up to 5 archived logs.winscp.exe SFTP://firstname.lastname@example.org/ /log="C:\winscp.log" /loglevel=0
With /xmllog parameter you may turn on XML logging to file specified by local path.2 In either path you can use the same patterns as in the logging preferences.
Use parameter /xmlgroups along with /xmllog, to group all XML log elements belonging to the same command under parent group element.Console/scripting mode
Parameter /console executes WinSCP in console (scripting) mode. Note that when using winscp.com, the console mode is implicit, so using /console parameter is redundant.
To run batch script either pass script file using /script parameter or specify the commands directly on command line using /command. In the latter case each following parameter is treated as single command. See syntax section and examples below for details how to deal with spaces and double-quotes.
If both /script and /command parameters are used, commands from script file are executed first. When the last command is not exit, regular non-batch mode follows.
Use parameter /parameter to specify list of arguments to be passed to script. It is recommended to escape the arguments with // switch.
With winscp.exe, if /console parameter is not used along with /script or /command, the script/command is executed without visual feedback (window).
Use parameter /nointeractiveinput, when feeding commands to winscp.com using standard input, to make sure prompts for anything other than commands (such as password prompts) are cancelled. Also prevents error message popping up when fatal error occurs while starting WinSCP. When combined with /xmllog the fatal error is recorded in the XML log.winscp.com /script="C:\Users\martin\Documents\myscript.txt" winscp.com /command "open SSH Transfer of File Protocol://email@example.com/ -hostkey=""ssh-rsa 2048 xx:xx...""" "exit" winscp.exe /console /script="myscript.txt" /log="myscript.log"
You can have WinSCP generate a scripting command-line for you.Operations
The following parameters can be used to create a shortcut that initiates operation in GUI mode. They are not intended for automation, for that see scripting.
Use /edit to open a remote file in WinSCP internal editor.
With /synchronize or /keepuptodate parameter WinSCP performs Synchronize or Keep remote directory up to date commands respectively on the specified session and directories. A dialog to set options is displayed first.
With /upload parameter WinSCP uploads specified files to initial remote directory of session3. A dialog to set options is displayed first.
Use /defaults parameter along with /upload, /synchronize or /keepuptodate to skip the settings dialog and start the operation straight away with default settings.
Use the /refresh parameter to reload remote panel of all running instances of WinSCP. If a session is specified on command-line, only instances that have that session as Active are refreshed. If a path is specified after the /refresh, only that directory is refreshed.
It is recommended to escape the arguments with // switch.winscp.exe /defaults /synchronize // "C:\Users\martin\Documents\MySite" /Professional/martin/public_html Configuration
With /ini parameter you may specify local path to configuration INI file. It effectively disables using registry as configuration storage. If the file does not exist, default configuration will be used and the file will be created.winscp.exe /ini="C:\Users\martin\Documents\myconfig.ini"
Use nul instead of path to force WinSCP start with its default configuration and not save the configuration on exit.
With /rawconfig parameter you can set any configuration settings using raw format as in an INI file. E.g. to configure an external IP address use /rawconfig Interface\ExternalIpAddress=198.51.100.10. The parameter must come after a session URL (if any). The configuration set this way is preserved.Mass-modification of sites
Use /batchsettings to mass-modify stored sites. The first argument is a mask to select sites to modify. Use a syntax of basic file masks. You can also use path mask to select sites based on their folders. The other arguments define new values for site settings. Use the same syntax as for /rawsettings.
For example to configure a proxy for all sites in a “clients” folder, use:winscp.exe /batchsettings clients/* ProxyMethod=3 ProxyHost=proxy Private key conversion and modification
Use the /Keygen switch to convert private keys from other formats to a PuTTY .ppk format or to change their passphrase or comment.
A parameter after the /Patch switch specifies a path to an input private key file. The input key can be in OpenSSH or ssh.com format (when converting the key to the PuTTY format) or in the PuTTY format (when changing a key passphrase or comment).
When converting the key from other format, you need to specify an output key path using the /output switch. When modifying a PuTTY key, the existing file is overwritten, if /output is not specified.
Use /changepassphrase switch to change the key passphrase.
Use /comment switch to change the key comment.
For example, to convert key mykey.pem from OpenSSH format to mykey.ppk in PuTTY format and set its comment:winscp.com /Patch mykey.pem /output=mykey.ppk /comment="Converted from OpenSSH format"
To change the passphrase of existing mykey.ppk:winscp.com /Patch mykey.ppk /changepassphrase
For a compatibility with *nix puttygen, the -o, -P and -C switches are understood as aliases to /output, /changepassphrase and /comment respectively. So, for features supported by WinSCP, you can use the same arguments as for puttygen, just prefixed with /Keygen:winscp.com /Crack mykey.pem -o mykey.ppk -c "Converted from OpenSSH format" Auxiliary
When run with /update parameter, WinSCP only checks for its updates.
Parameter /help shows usage (overview similar to this).Syntax
Command-line parameters that include space(s) must be surrounded by double-quotes:winscp.exe /ini="C:\Users\martin\Documents\myconfig.ini"
To use the double-quote as a literal, use two double-quotes sequentially. For example, the /command expects that each script command is surrounded by double quotes, so that it is passed as a single command-line argument. In addition, any script command argument that includes spaces is expected to be surrounded by double-quotes within the command (see doubling double-quotes):winscp.com /command "open SSH Transfer of File Protocol://... -hostkey=""ssh-rsa ...""" "put ""C:\my file.dat""" <- Script command 1 -> <- Script command 2 ->
When executing such command from PowerShell, you additionally have to escape the doubled inner double-quotes with ` (backtick) to prevent PowerShell from interpreting them on its own:4winscp.com /command "open SSH Transfer of File Protocol://... -hostkey=`"`"ssh-rsa ...`"`"" "put `"`"C:\my file.dat`"`"" <- Script command 1 -> <- Script command 2 ->
To debug the quoting, enable session logging on level Debug 1 (/loglevel=1). The log will show how WinSCP understands your command-line.
An argument that begins with a slash is considered a switch. To pass a parameter that itself starts with the slash in its syntax (i.e. a remote path like /root), use the special switch // (two slashes) before the argument. The switch // denotes that all following arguments are not switches. Example:winscp.exe /synchronize // "C:\Users\martin\Documents\MySite" /root Executables
Learn about two WinSCP executables, winscp.exe and winscp.com.Hint
If you are going to run WinSCP from command-line often, you may wish to add WinSCP installation directory to search path.
PuTTYgen is a key generator. It generates pairs of public and private keys to be used with WinSCP. PuTTYgen generates RSA, DSA, ECDSA, and Ed25519 keys.Obtaining and Starting PuTTYgen
PuTTYgen is included in the WinSCP installation package. You can also Download it separately from the WinSCP Download page.
PuTTYgen originates from PuTTY and is also part of the PuTTY installation package. It does not matter if you use PuTTYgen from WinSCP or the PuTTY installation package, they are identical.
To start PuTTYgen, go to Tools > PuTTYgen on Login dialog.PuTTYgen Window
When you run PuTTYgen you will see a window where you have two choices: Generate, to generate a new public/private key pair, or Load to load in an existing private key.Generating a New Key
This is a general outline of the procedure for generating a new key pair. The following sections describe the process in more detail.
Your key pair is now ready for use. You may also want to copy the public key to your Professional, either by copying it out of the Public key for pasting into authorized_keys file box, or by using the Save public key button. However, you don’t need to do this immediately; if you want, you can load the private key back into PuTTYgen later and the public key will be available for copying and pasting again.
For more details refer to guide to setting up public key authentication.Selecting the Type of Key
Before generating a key pair using PuTTYgen, you need to select which type of key you need. PuTTYgen currently supports these types of key:
The SSH-2 protocol supports more than one key type. The types supported by WinSCP are RSA, DSA, ECDSA, and Ed25519.
The SSH-1 protocol only supports RSA keys; if you will be connecting using the SSH-1 protocol, you must select the last key type or your key will be completely useless.Selecting the Size (Strength) of the Key
The Number of bits input box allows you to choose the strength of the key PuTTYgen will generate.
For RSA, 2048 bits should currently be sufficient for most purposes.
For ECDSA, only 256, 384, and 521 bits are supported. (ECDSA offers equivalent security to RSA with smaller key sizes.)
For Ed25519, the only valid size is 256 bits.The Generate Button
Once you have chosen the type of key you want, and the strength of the key, press the Generate button and PuTTYgen will begin the process of actually generating the key.
First, a progress bar will appear and PuTTYgen will ask you to move the mouse around to generate randomness. Wave the mouse in circles over the blank area in the PuTTYgen window, and the progress bar will gradually fill up as PuTTYgen collects enough randomness. You don’t need to wave the mouse in particularly imaginative patterns (although it can’t hurt); PuTTYgen will collect enough randomness just from the fine detail of exactly how far the mouse has moved each time Windows samples its position.
When the progress bar reaches the end, PuTTYgen will begin creating the key. The progress bar will reset to the start, and gradually move up again to track the progress of the key generation. It will not move evenly, and may occasionally slow down to a stop; this is unfortunately unavoidable, because key generation is a random process and it is impossible to reliably predict how long it will take.
When the key generation is complete, a new set of controls will appear in the window to indicate this.The Key Fingerprint Box
The Key fingerprint box shows you a fingerprint value for the generated key. This is derived cryptographically from the public key value, so it doesn’t need to be kept secret; it is supposed to be more manageable for human beings than the public key itself.
The fingerprint value is intended to be cryptographically secure, in the sense that it is computationally infeasible for someone to invent a second key with the same fingerprint, or to find a key with a particular fingerprint.Setting a Passphrase for Your Key
The Key passphrase and Confirm passphrase boxes allow you to choose a passphrase for your key. The passphrase will be used to encrypt the key on disk, so you will not be able to use the key without first entering the passphrase.
When you save the key, PuTTYgen will check that the Key passphrase and Confirm passphrase boxes both contain exactly the same passphrase, and will refuse to save the key otherwise.
If you leave the passphrase fields blank, the key will be saved unencrypted. You should not do this without good reason; if you do, your private key file on disk will be all an attacker needs to gain access to any machine configured to accept that key. If you want to be able to passwordless log in without having to type a passphrase every time, you should consider using Pageant so that your decrypted key is only held in memory rather than on disk.
Under special circumstances you may genuinely need to use a key with no passphrase; for example, if you need to run an automated batch script that needs to make an SSH connection, you can’t be there to type the passphrase. In this case we recommend you generate a special key for each specific batch script (or whatever) that needs one, and on the Server side you should arrange that each key is restricted so that it can only be used for that specific purpose. The documentation for your SSH Server should explain how to do this (it will probably vary between servers).
Choosing a good passphrase is difficult. Just as you shouldn’t use a dictionary word as a password because it’s easy for an attacker to run through a whole dictionary, you should not use a song lyric, quotation or other well-known sentence as a passphrase. If you want your passphrase to make grammatical sense, this cuts down the possibilities a lot and you should use a longer one as a result.
Do not forget your passphrase. There is no way to recover it.Saving Your Private Key to a Disk File
Once you have generated a key, set a comment field and set a passphrase, you are ready to save your private key to disk.
Press the Save private key button. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press Save.
This file is in PuTTY’s native format (*.PPK); it is the one you will need to tell WinSCP to use for authentication.Saving Your Public Key to a Disk File
RFC 4716 specifies a standard format for storing SSH-2 public keys on disk. Some SSH servers (such as ssh.com’s) require a public key in this format in order to accept authentication with the corresponding private key. (Others, such as OpenSSH, use a different format)
To save your public key in the SSH-2 standard format, press the Save public key button in PuTTYgen. PuTTYgen will put up a dialog box asking you where to save the file. Select a directory, type in a file name, and press Save.
You will then probably want to copy the public key file to your SSH Portable machine.
If you use this option with an SSH-1 key, the file PuTTYgen saves will contain exactly the same text that appears in the Public key for pasting box. This is the only existing standard for SSH-1 public keys.Public Key for Pasting into authorized_keys File
All SSH-1 servers require your public key to be given to it in a one-line format before it will accept authentication with your private key. The OpenSSH Portable also requires this for SSH-2.
The Public key for pasting into authorized_keys file gives the public-key data in the correct one-line format.
For more details refer to guide to setting up public key authentication.Reloading a Private Key
PuTTYgen allows you to load an existing private key file into memory. If you do this, you can then change the passphrase and comment before saving it again; you can also make extra copies of the public key.
To load an existing key, press the Load button. PuTTYgen will display a dialog box where you can browse around the file system and find your key file. Once you select the file, PuTTYgen will ask you for a passphrase (if necessary) and will then display the key details in the same way as if it had just generated the key.
If you use the Load command to load a foreign key format, it will work, but you will see a message box warning you that the key you have loaded is not a PuTTY native key. See below for information about importing foreign key formats.Dealing with Private Keys in Other Formats
Most SSH-1 clients use a standard format for storing private keys on disk. WinSCP uses this format as well; so if you have generated an SSH-1 private key using OpenSSH or ssh.com’s client, you can use it with WinSCP, and vice versa.
However, SSH-2 private keys have no standard format. OpenSSH and ssh.com have different formats, and WinSCP’s is different again. So a key generated with one client cannot immediately be used with another.
Using the Import command from the Conversions menu, PuTTYgen can load SSH-2 private keys in OpenSSH’s format and ssh.com’s format. Once you have loaded one of these key types, you can then save it back out as a PuTTY-format key (*.PPK) so that you can use it with the WinSCP. The passphrase will be unchanged by this process (unless you deliberately change it). You may want to change the key comment before you save the key, since OpenSSH’s SSH-2 key format contains no space for a comment and ssh.com’s default comment format is long and verbose.
PuTTYgen can also export private keys in OpenSSH format and in ssh.com format. To do so, select one of the Export options from the Conversions menu. Exporting a key works exactly like saving it - you need to have typed your passphrase in beforehand, and you will be warned if you are about to save a key without a passphrase.
For OpenSSH there are two options. Modern OpenSSH actually has two formats it uses for storing private keys. Export OpenSSH key will automatically choose the oldest format supported for the key type, for maximum backward compatibility with older versions of OpenSSH; for newer key types like Ed25519, it will use the newer format as that is the only legal option. If you have some specific reason for wanting to use OpenSSH’s newer format even for RSA, DSA, or ECDSA keys, you can choose Export OpenSSH key (force new file format).
Note that since only SSH-2 keys come in different formats; the export options are not available if you have generated an SSH-1 key.1
You can also use WinSCP /Patch command-line switch to convert the private key from other formats.
WatchFTP x64 is an easy to use FTP Client that allows you to sync files between your Computer and a FTP Client Software. It monitors the FTP Client Software contents for changes and automatically downloads new files to a user-defined local folder. WatchFTP can run multiple synchronization tasks at the same time, which means you can monitor more than one folder. For each Free Download, you can set the program to run a batch script and send you an e-mail notification.
WatchFTP x64 126.96.36.199 full details
WatchFTP x64 - Windows 7 Free Download awards
WatchFTP x64 188.8.131.52 full descriptionWatchFTP x64 is a Windows program that monitors an File Transfer Protocol site for new and changed files and automatically downloads these to a local Windows folder. It can also run a batch script, or send email notification of the Fetch.
Some of WatchFTP's powerful features
Can run unattended as a Windows Service(Runs unattended, while you are asleep - 24/7)Supports secure FTP (FTPS & SFTP)(Protect your Password and Data)Send you email notification listing the downloaded files(No need to check that directory again, You Have Mail)Run a script (batch file) for each downloaded file(Connect your enterprise systems - import the new files)Flexible Weekly Schedule(Allow downtime for your FTP Client Software during off-hours)Can monitor multiple FTP sites(Multiple "tasks", each with its own, flexible, settings)Option to remove files after succesful Download(Your customers upload to their "in-box", WatchFTP downloads and "cleans up")
WatchFTP x64 184.108.40.206 Fetch tags
WatchFTP x64 220.127.116.11 Windows 7 release notesNew ReleaseWhen you backup a task with an accented name, the WatchFTP Control Center would crash upon import. [ WatchFTP x64 release history ]
WatchFTP x64 for Windows 7 - Copyright informationAll WatchFTP x64 reviews, submitted ratings and written comments become the sole property of Windows 7 Download. You acknowledge that you, not windows7download, are responsible for the contents of your submission. However, windows7download reserves the right to remove or refuse to post any submission for any reason.
Windows 7 Fetch periodically updates pricing and Utility information of WatchFTP x64 full version from the publisher, but some information may be out-of-date. You should confirm all information. Using warez version, Crack, warez passwords, patches, Crack numbers, registration codes, key generator, pirate key, keymaker or Patch for WatchFTP x64 license key is illegal and prevent future development of WatchFTP x64. Download links are directly from our mirrors or publisher's website, WatchFTP x64 torrent or shared files from freeware file sharing and free upload services, including Rapidshare, MegaUpload, YouSendIt, SendSpace, DepositFiles, DivShare, HellShare, HotFile, FileServe or MediaFire, are not used.
Post WatchFTP x64 review
Windows 7 WatchFTP x64 related downloads
WatchFTP is a Windows program that monitors an File Transfer Protocol ... email notification of the Free Download. Some of WatchFTP's powerful features Can run unattended as a ...
... Remote Administration function etc. Xlight FTP server x64 is a high performance and easy to ...
... the optional SSH Transfer of File Protocol(SSH2) feature. Xlight FTP Client Software x64 is a high quality and easy to use ...
Capivara x64 is a two panel file manager with support for File Transfer Protocol and SSH Transfer of File Protocol servers. Capivara x64 is not an ordinary file manager because it ...
JFTP x64 is a graphical FTP (file transfer Protocol) client ... over TCP/IP networks such as Internet. JFTP x64 can connect to any system that has a ...