Differences
This shows you the differences between the selected revisions of the page.
| ui_import 2011-05-24 | ui_import 2024-09-23 (current) | ||
| Line 1: | Line 1: | ||
| - | ====== Importing Stored Sessions from PuTTY ====== | + | ====== Importing Sites ====== |
| - | WinSCP allows you to import stored sessions from [[&url(putty)|PuTTY SSH client]]. | + | WinSCP allows you to import sites from [[&url(putty)|PuTTY SSH client]], [[https://www.9bis.net/kitty/|KiTTY SSH client]], [[https://filezilla-project.org/|FileZilla FTP/SFTP client]], OpenSSH ''config'' file, [[config|WinSCP INI file]] and host keys from OpenSSH ''known_hosts'' file. |
| &screenshotpict(import) | &screenshotpict(import) | ||
| - | To open //Import session from PuTTY// dialog use //Tools// button on //[[ui_login_stored_sessions|Stored sessions tab]]// of Login dialog. | + | To open //Import session// dialog go to //Tools > Import Sites// on [[ui_login|Login dialog]]. |
| - | You will receive list of all sessions created in PuTTY. In the seconds column of the list you will see a protocol that is associated with the session. Next to the session name there is a checkbox. Use it to select sessions you would like to import. By default WinSCP will select only SSH sessions for which there is no WinSCP session with the same name. You can alter the selection as you like. You can even select session with other protocols (like Telnet) if you know that the server supports SSH as well. | + | On the dialog, select if you want to import from PuTTY, KiTTY, FileZilla, OpenSSH ''config'', WinSCP INI file or ''known_hosts'' files. |
| - | The checkbox //Import cached host keys for checked sessions// makes WinSCP import SSH host keys from PuTTY cache for hostnames from all selected sessions. So you do not need to confirm again the SSH host keys that you have confirmed in PuTTY already. | + | You will receive list of all sites/host keys stored in the selected application or configuration file. Next to each site name there is a checkbox. Use it to select sites/keys you would like to import. By default WinSCP selects only sites with supported protocol,((It does not select Serial, Telnet, Rlogin, SUPDUP, Raw and Bare ssh-connection sessions from PuTTY/KiTTY.)) for which there is no WinSCP site with the same name. You can alter the selection as you like.· |
| - | When you finish your selection, press //OK// to import the sessions. Note that when the name of imported session collides with name of an existing session, WinSCP appends number to end of the name to name it unique.·For session options that PuTTY does not have, WinSCP will use the [[session_configuration#default|defaults]]. | + | ===== PuTTY/KiTTY ===== |
| + | |||
| + | For PuTTY/KiTTY, WinSCP looks for sites in registry. | ||
| + | |||
| + | ===== FileZilla ===== | ||
| + | |||
| + | For FileZilla, WinSCP looks for sites in ''C:\Users\username\AppData\Roaming\FileZilla\sitemanager.xml''. &winpath | ||
| + | |||
| + | ===== [[ini]] INI file ===== | ||
| + | |||
| + | You can use this option to selectively import only some sites from WinSCP INI [[config|configuration]] file (as opposed to [[config#import|importing whole configuration]]). Use //Browse// button to browse for the location of the INI file. | ||
| + | |||
| + | &beta_feature | ||
| + | |||
| + | ===== [[openssh_config]] OpenSSH config ===== | ||
| + | |||
| + | For [[https://man.openbsd.org/ssh_config|OpenSSH ''config'' file]], WinSCP looks to ''C:\Users\username\.ssh\config''. In the file, it looks for all ''Host'' directives with specific hostname and imports them as sites to WinSCP. | ||
| + | |||
| + | When resolving site settings, it considers all ''Host'' directives, even those with wildcards. The following directives are recognized: ''AddressFamily'', ''BindAddress'', ''Compression'', ''ForwardAgent'', ''GSSAPIAuthentication'', ''GSSAPIDelegateCredentials'', ''Hostname'', ''IdentityFile'', ''KbdInteractiveAuthentication'', ''Port'', ''ProxyJump'' (single jump only) and ''User''. | ||
| + | |||
| + | When private key is found in the ''IdentityFile'' directive, WinSCP will offer you to convert the key to PuTTY format, unless a key file with the same name and ''.ppk'' extension exists already. Additionally, if certificate file with the same name((but ''-cert.pub'' or ''.pub-aadcert.pub'' //(latest beta only)// &beta suffixes.)) is found, it will be automatically added to the converted key file. | ||
| + | |||
| + | ===== [[openssh_known_hosts]] OpenSSH known_hosts ===== | ||
| + | |||
| + | For OpenSSH ''known_hosts'' files, WinSCP looks to ''C:\Users\username\.ssh\known_hosts''. &winpath You can also paste hosts key in OpenSSH format from clipboard using //Paste// button. | ||
| + | |||
| + | WinSCP imports also SSH host keys from the source application cache for hostnames from all selected sites. So you do not need to [[ssh_verifying_the_host_key|verify]] again the SSH host keys that you have verified in the other application already. | ||
| + | |||
| + | When you finish your selection, press //OK// to import the sites. Note that when the name of imported site collides with name of an existing site, WinSCP appends number to the end of the name to name it unique. | ||
| + | |||
| + | For session options that the source application does not have, WinSCP will use the [[session_configuration#default|defaults]]. | ||