Differences
This shows you the differences between the selected revisions of the page.
| 2014-06-17 | 2014-07-14 | ||
| sections (martin) | 5.6 Bug 816 Passphrase can be provided on command line/in scripting and .NET assembly. (martin) | ||
| Line 8: | Line 8: | ||
| 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]]). | 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]]). | ||
| - | WinSCP does not support providing the passphase from [[commandline|command line]] or by other means allowing automation. Anyway, this would not bring substantial advantage over unprotected key as the passphrase would need to be stored too (in a script), probably on the same data storage as the key. | + | //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 |