Differences
This shows you the differences between the selected revisions of the page.
| integration_app 2013-07-18 | integration_app 2019-10-23 (current) | ||
| Line 5: | Line 5: | ||
| ===== PuTTY ===== | ===== PuTTY ===== | ||
| In addition to being based on source code of this popular SSH client, WinSCP | In addition to being based on source code of this popular SSH client, WinSCP | ||
| - | can also share site settings with it. | + | can also [[integration_putty|share site settings with it]]. |
| - | + | ||
| - | ==== Importing Sites ==== | + | |
| - | To [[ui_import|import sites (stored sessions)]] &beta from PuTTY go to | + | |
| - | //[[ui_login_stored_sessions#tools_button|Tools > Import Sites]]// on | + | |
| - | //Sites/Stored sessions page// &beta of Login dialog. | + | |
| - | + | ||
| - | ==== [[open_putty]] Opening Current Session in PuTTY ==== | + | |
| - | If WinSCP's limited ability to [[remote_command|execute remote commands]] | + | |
| - | does not meet your needs, you can let WinSCP open a shell session on the | + | |
| - | same server in a PuTTY client. Go to //Commands > Open in PuTTY//. | + | |
| - | + | ||
| - | By default, WinSCP creates temporary site settings for PuTTY (under the name "WinSCP temporary session"). The site settings will contain only the options | + | |
| - | known by WinSCP, mostly connection options. It will particularly lack | + | |
| - | any terminal options, so the defaults (//Default Settings// profile) will apply. | + | |
| - | + | ||
| - | If you want to configure your own options, you can save PuTTY site settings | + | |
| - | with the same name as a WinSCP site. WinSCP will then instruct PuTTY | + | |
| - | to open that session (It will not export any settings, nor a connection | + | |
| - | options). | + | |
| - | + | ||
| - | If WinSCP cannot find the PuTTY executable in the default path (particularly when you are using derived version of PuTTY) you can specify the path in [[ui_pref_integration_app|preferences]]. Optionally you can also instruct WinSCP to send the session password ([[security_credentials|if known]]) to PuTTY. However a better approach would be to use [[public key]] authentication together with [[integration_app#pageant|Pageant]]. | + | |
| - | + | ||
| - | You can also set up WinSCP to //[[ui_pref_integration_app|Automatically open new sessions in PuTTY]]//. | + | |
| - | + | ||
| - | ==== [[putty_startup_directory]] Opening PuTTY in the Same Directory ==== | + | |
| - | If you want PuTTY to open in the same directory as WinSCP, you need to replace its startup command using ''-m'' argument. The syntax of the startup command would differ with the remote environment, particularly with operating system and shell. | + | |
| - | + | ||
| - | For example with Unix-like system and ''bash'' shell the command will be like (note the ''!/'' [[ui_pref_integration_app#client_path|pattern]] to pass current remote path): | + | |
| - | + | ||
| - | <code> | + | |
| - | cd "!/" ; /bin/bash -login | + | |
| - | </code> | + | |
| - | + | ||
| - | As PuTTY needs to have the startup command to be stored in a file, you need to make use of ''!`command`'' [[ui_pref_integration_app#client_path|pattern]] to store the above command into a temporary file. Also as use of ''-m'' switch implies a non-interactive terminal, you need to force an interactive terminal back using ''-t'' switch. | + | |
| - | + | ||
| - | Complete PuTTY command line for this will be like (change the shell path according to your system and preferences): | + | |
| - | + | ||
| - | <code> | + | |
| - | %PROGRAMFILES%\PuTTY\putty.exe -t -m "%TEMP%\putty.txt" !`cmd.exe /c echo cd "!/" ; /bin/bash -login > "%TEMP%\putty.txt"` | + | |
| - | </code> | + | |
| - | + | ||
| - | ==== Download PuTTY ==== | + | |
| - | For your convenience you can [[&download#putty|download PuTTY]] also from our download page. | + | |
| - | + | ||
| - | ==== [[kitty]] Using KiTTY Instead of PuTTY ==== | + | |
| - | If you want to use [[http://kitty.9bis.net/|KiTTY]], instead of PuTTY, you need to configure path to KiTTY executable in [[ui_pref_integration_app|preferences]]. | + | |
| - | + | ||
| - | When using KiTTY in registry (non-portable) mode, you also need to specify KiTTY registry key in preferences. | + | |
| - | + | ||
| - | When using KiTTY in portable mode, you need to specify pattern ''!U@!@'' in terminal client path as an alternative way to pass hostname and username to KiTTY: | + | |
| - | + | ||
| - | <code> | + | |
| - | kitty.exe !U@!@ | + | |
| - | </code> | + | |
| - | + | ||
| - | To open KiTTY in the same directory as WinSCP, you can use either the same [[integration_app#putty_startup_directory|technique as with PuTTY]]; or use KiTTY's ''-cmd'' switch to avoid use of temporary file: | + | |
| - | + | ||
| - | <code> | + | |
| - | kitty.exe -cmd "cd ""!/""" !U@!@ | + | |
| - | </code> | + | |
| ===== External Editor ===== | ===== External Editor ===== | ||
| - | For editing files in WinSCP you can configure it to use your favourite [[ui_pref_editor|editor]]. | + | For editing files in WinSCP you can configure it to use your [[integration_editor|favorite editor]]. |
| ===== Pageant ===== | ===== Pageant ===== | ||
| Learn how to use the [[ui_pageant|Pageant]] (PuTTY's SSH authentication agent) application for public key authentication. | Learn how to use the [[ui_pageant|Pageant]] (PuTTY's SSH authentication agent) application for public key authentication. | ||
| - | ===== FileZilla ===== | + | ===== [[filezilla]] FileZilla ===== |
| - | &beta_feature | + | To [[ui_import|import sites]] from FileZilla go to |
| + | //Tools > Import Sites// on [[ui_login|Login dialog]]. | ||
| - | To [[ui_import|import sites (stored sessions)]] &beta from FileZilla go to | + | ===== Password Managers ===== |
| - | //[[ui_login_stored_sessions#tools_button|Tools > Import Sites]]// on | + | If you use password manager, such as [[integration_keepass|KeePass]], you can use them as site manager to WinSCP. |
| - | //Sites/Stored sessions page// &beta of Login dialog. | + | |