Differences
This shows you the differences between the selected revisions of the page.
| 2023-02-17 | 2023-05-24 | ||
| certificate is automatically added to the converted key file (martin) | 6.1 stable released (martin) | ||
| 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, KiTTY, &beta FileZilla, OpenSSH ''config'' or ''known_hosts'' files. | + | On the dialog, select if you want to import from PuTTY, KiTTY, FileZilla, OpenSSH ''config'' or ''known_hosts'' files. |
| 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. | 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. | ||
| Line 14: | Line 14: | ||
| For PuTTY/KiTTY, WinSCP looks for sites in registry. | For PuTTY/KiTTY, WinSCP looks for sites in registry. | ||
| - | |||
| - | //Direct import from KiTTY is available in the latest beta version only. In the current stable release, you need to first configure WinSCP to look for [[ui_pref_integration_app|KiTTY registry keys]] and then choose to import from PuTTY.// &beta | ||
| ===== FileZilla ===== | ===== FileZilla ===== | ||
| Line 27: | Line 25: | ||
| 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 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. //In the latest beta version,// &beta additionally, if certificate file with the same name (but ''-cert.pub'' suffix) is found, it will be automatically added to the converted key file. | + | 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'' suffix) is found, it will be automatically added to the converted key file. |
| ===== [[openssh_known_hosts]] OpenSSH known_hosts ===== | ===== [[openssh_known_hosts]] OpenSSH known_hosts ===== | ||