Differences
This shows you the differences between the selected revisions of the page.
| 2014-09-03 | 2017-06-28 | ||
| import locations (martin) | 5.10.2 Bug 1542: Host keys can be imported from OpenSSH known_hosts file (martin) | ||
| Line 1: | Line 1: | ||
| ====== Importing Sites ====== | ====== Importing Sites ====== | ||
| - | WinSCP allows you to import sites from [[&url(putty)|PuTTY SSH client]] and [[https://filezilla-project.org/|FileZilla FTP client]]. | + | WinSCP allows you to import sites from [[&url(putty)|PuTTY SSH client]], [[https://filezilla-project.org/|FileZilla FTP client]] and host keys from OpenSSH ''known_hosts'' file (&beta_feature). |
| &screenshotpict(import) | &screenshotpict(import) | ||
| Line 7: | Line 7: | ||
| To open //Import session// dialog go to //Tools > Import Sites// on [[ui_login|Login dialog]]. | To open //Import session// dialog go to //Tools > Import Sites// on [[ui_login|Login dialog]]. | ||
| - | On the dialog, select if you want to import from PuTTY or FileZilla. | + | On the dialog, select if you want to import from PuTTY, FileZilla or ''known_hosts''. |
| - | You will receive list of all sites created in the selected application. Next to each site name there is a checkbox. Use it to select sites you would like to import. By default WinSCP selects only sites with supported protocol ((It does not select Raw, Telnet, Rlogin and Serial sessions from PuTTY.)), for which there is no WinSCP site with the same name. You can alter the selection as you like. | + | You will receive list of all sites/host keys stored in the selected application. 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 Raw, Telnet, Rlogin and Serial sessions from PuTTY.)), for which there is no WinSCP site with the same name. You can alter the selection as you like. |
| For PuTTY, WinSCP looks for sites in registry. If you use PuTTY clone, you can configure WinSCP to look for [[ui_pref_integration_app|its registry keys]] instead. | For PuTTY, WinSCP looks for sites in registry. If you use PuTTY clone, you can configure WinSCP to look for [[ui_pref_integration_app|its registry keys]] instead. | ||
| Line 15: | Line 15: | ||
| For FileZilla, WinSCP looks for sites in ''C:\Users\username\AppData\Roaming\FileZilla\sitemanager.xml''. &winpath | For FileZilla, WinSCP looks for sites in ''C:\Users\username\AppData\Roaming\FileZilla\sitemanager.xml''. &winpath | ||
| - | The checkbox //Import cached host keys for checked sites// makes WinSCP import 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. | + | 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. |
| + | |||
| + | //In versions prior to the latest beta version,// the checkbox //Import cached host keys for checked sites// makes WinSCP import 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. //The latest beta version// imports the host keys always. | ||
| 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. | 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. | ||