Differences
This shows you the differences between the selected revisions of the page.
| ui_pref_security 2023-10-10 | ui_pref_security 2026-04-02 (current) | ||
| Line 13: | Line 13: | ||
| Use //Change master password// to change master password. [[ui_master_password_change|Master password setting dialog]] will appear. | Use //Change master password// to change master password. [[ui_master_password_change|Master password setting dialog]] will appear. | ||
| - | ===== [[session_password]] Session Password ===== | + | ===== [[authentication]] Authentication ===== |
| Uncheck the //Remember password for duration of the session// checkbox to avoid your password (or private key passphrase) being [[security_credentials#password_memory|stored in the memory]] for a duration of the session. You will be prompted for your password/passphrase again, when reconnecting a lost connection and for background transfers. | Uncheck the //Remember password for duration of the session// checkbox to avoid your password (or private key passphrase) being [[security_credentials#password_memory|stored in the memory]] for a duration of the session. You will be prompted for your password/passphrase again, when reconnecting a lost connection and for background transfers. | ||
| + | |||
| + | By default, WinSCP uses [[ui_pageant|PuTTY Pageant]] as an //Authentication agent//. You can configure it to use //OpenSSH ssh-agent// instead. &beta_feature. | ||
| ===== [[authorities]] Trusted Host Certification Authorities ===== | ===== [[authorities]] Trusted Host Certification Authorities ===== | ||
| In some environments, the SSH host keys for a lot of servers will all be signed in turn by a central "certification authority" ("CA" for short). This simplifies host key configuration for users, because if they configure their SSH client to accept host keys certified by that CA, then they don't need to individually confirm each host key the first time they connect to that server.((&puttydoccite)) | In some environments, the SSH host keys for a lot of servers will all be signed in turn by a central "certification authority" ("CA" for short). This simplifies host key configuration for users, because if they configure their SSH client to accept host keys certified by that CA, then they don't need to individually confirm each host key the first time they connect to that server.((&puttydoccite)) | ||
| - | In this section you can configure what CAs WinSCP will accept signatures from. &beta_feature | + | In this section you can configure what CAs WinSCP will accept signatures from. |
| If you check //Load authorities from PuTTY//, WinSCP will load the trusted authorities from PuTTY.((From its Windows registry key. So this configuration won't be [[portable]].)) WinSCP will display loaded authorities in the list below. But you will not be able to configure the authorities in WinSCP. Instead you can press //Edit in PuTTY// button to open PuTTY's trusted authorities configuration window. | If you check //Load authorities from PuTTY//, WinSCP will load the trusted authorities from PuTTY.((From its Windows registry key. So this configuration won't be [[portable]].)) WinSCP will display loaded authorities in the list below. But you will not be able to configure the authorities in WinSCP. Instead you can press //Edit in PuTTY// button to open PuTTY's trusted authorities configuration window. | ||