Differences
This shows you the differences between the selected revisions of the page.
| 2014-07-28 | 2014-07-28 | ||
| typo in comment (martin) | 5.6 bug 160 webdav (martin) | ||
| Line 19: | Line 19: | ||
| Note that the first connection to an SSH server requires [[scripting#hostkey|verification of the host key]]. | Note that the first connection to an SSH server requires [[scripting#hostkey|verification of the host key]]. | ||
| - | Also the first connection to FTPS host with [[ftps#certificate|certificate]] signed by untrusted authority requires verification of the certificate. | + | Also the first connection to FTPS or WebDAVS host with [[ftps#certificate|certificate]] signed by untrusted authority requires verification of the certificate. |
| ~~AD~~ | ~~AD~~ | ||
| Line 98: | Line 98: | ||
| You can find the key fingerprint on [[ui_fsinfo|Server and Protocol Information Dialog]]. You can also copy the key fingerprint to clipboard from the confirmation prompt on the first (interactive) connection using //Copy Key// button. //Learn more about [[faq_script_hostkey|obtaining host key fingerprint]]//. | You can find the key fingerprint on [[ui_fsinfo|Server and Protocol Information Dialog]]. You can also copy the key fingerprint to clipboard from the confirmation prompt on the first (interactive) connection using //Copy Key// button. //Learn more about [[faq_script_hostkey|obtaining host key fingerprint]]//. | ||
| - | [[ftps#certificate|FTPS certificate]] signed by untrusted authority may also need to be verified. To automate the verification in script, use ''-certificate'' switch of ''[[scriptcommand_open|open]]'' command to accept the expected certificate automatically. | + | FTPS/WebDAVS [[ftps#certificate|TLS/SSL certificate]] signed by untrusted authority may also need to be verified. To automate the verification in script, use ''-certificate'' switch of ''[[scriptcommand_open|open]]'' command to accept the expected certificate automatically. |
| Line 105: | Line 105: | ||
| If you are going to run the script under a different account (for example using the Windows scheduler), don't forget that WinSCP still needs to access its configuration. Note that when using registry as [[config|configuration storage]], the settings are accessible only for your Windows account, so in such a case you may need to either transfer the configuration from your account registry to the other account's registry or use the [[config|INI file]] instead. | If you are going to run the script under a different account (for example using the Windows scheduler), don't forget that WinSCP still needs to access its configuration. Note that when using registry as [[config|configuration storage]], the settings are accessible only for your Windows account, so in such a case you may need to either transfer the configuration from your account registry to the other account's registry or use the [[config|INI file]] instead. | ||
| - | Note that the configuration also includes [[scripting#hostkey|verified SSH host keys]] and [[ftps#certificate|FTPS certificates]]. | + | Note that the configuration also includes [[scripting#hostkey|verified SSH host keys]] and FTPS/WebDAVS [[ftps#certificate|TLS/SSL certificates]]. |
| ===== [[configuration]] Sharing Configuration with Graphical Mode ===== | ===== [[configuration]] Sharing Configuration with Graphical Mode ===== | ||