Differences
This shows you the differences between the selected revisions of the page.
integration_app 2008-04-08 | 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 session settings with it. | + | can also [[integration_putty|share site settings with it]]. |
- | ==== Importing Session List ==== | + | ===== External Editor ===== |
- | To import list of stored sessions from PuTTY use | + | For editing files in WinSCP you can configure it to use your [[integration_editor|favorite editor]]. |
- | //[[ui_login_stored_sessions#tools_button|Tools button > Import]]// on | + | |
- | //Stored sessions tab// of Login dialog. | + | |
- | ==== Opening Current Session in PuTTY ==== | + | ===== Pageant ===== |
- | If WinSCP's limited ability to [[remote_command|execute remote commands]] | + | Learn how to use the [[ui_pageant|Pageant]] (PuTTY's SSH authentication agent) application for public key authentication. |
- | 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 session settings for PuTTY (under the name "WinSCP temporary session"). The session settings will contain only the options | + | ===== [[filezilla]] FileZilla ===== |
- | known by WinSCP, mostly connection options, but it will particularly lack | + | To [[ui_import|import sites]] from FileZilla go to |
- | any terminal options, so the defaults will apply. | + | //Tools > Import Sites// on [[ui_login|Login dialog]]. |
- | If you want to configure your own options, you can save PuTTY session settings | + | ===== Password Managers ===== |
- | with the same name as a WinSCP session. WinSCP will then instruct PuTTY | + | If you use password manager, such as [[integration_keepass|KeePass]], you can use them as site manager to WinSCP. |
- | to open that session (It will not export any settings, not a connection | + | |
- | options). | + | |
- | If WinSCP cannot find the PuTTY executable in the default path, you can specify the path in [[ui_pref_integration_app|preferences]]. Optionally you can also instruct WinSCP to send the session password (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]]//. | ||
- | |||
- | Note that U3 version of WinSCP comes with PuTTY path preconfigured to temporary folder, where U3 drive extracts the PuTTY for U3. As the extraction happens on the first execution, the //Open in PuTTY// command would not work until you execute PuTTY at least once manually from U3 Launchpad. | ||
- | |||
- | ===== External Editor ===== | ||
- | For editing files in WinSCP you can configure it to use your favourite [[ui_pref_editor|editor]]. | ||
- | |||
- | ===== Pageant ===== | ||
- | Learn how to use the [[public_key|Pageant]] (PuTTY's SSH authentication agent) application for public key authentication. |