Differences
This shows you the differences between the selected revisions of the page.
| 2014-07-14 | 2015-02-18 | ||
| 5.6 Bug 816 Passphrase can be provided on command line/in scripting and .NET assembly. (martin) | releasing 5.7 stable, removing &beta tags (or replacing with &recent) (martin) | ||
| Line 6: | Line 6: | ||
| ===== Automating Private Key Authentication ===== | ===== Automating Private Key Authentication ===== | ||
| - | If you need to avoid entering the passphrase to automate a task (such as with [[scripting]] or when using [[library|.NET assembly]]) and using authentication agent is not suitable for you, you can store the key unprotected (without an passphrase). Note that this imposes security risk, if someone gains access to the key. You should consider restricting access to the unprotected private key file to the local account that runs the script only (using [[http://technet.microsoft.com/en-us/library/cc770962.aspx|Windows file system permissions]]). | + | You can specify the passphrase using ''-passphrase''; switch of ''[[scriptcommand_open|open]]'' command in scripting and using ''[[library_sessionoptions|SessionOptions.SshPrivateKeyPassphrase]]'' in .NET assembly. |
| + | |||
| + | Alternatively you can store the key unprotected (without an passphrase). Note that this imposes security risk, if someone gains access to the key. You should consider restricting access to the unprotected private key file to the local account that runs the script only (using [[http://technet.microsoft.com/en-us/library/cc770962.aspx|Windows file system permissions]]). | ||
| - | //With WinSCP 5.6 beta, you can specify passphrase using ''-passphrase'' switch of ''[[scriptcommand_open|open]]'' command in scripting and using ''[[library_sessionoptions|SessionOptions.SshPrivateKeyPassphrase]]'' in .NET assembly.// &beta | ||