Differences
This shows you the differences between the selected revisions of the page.
| custom_distribution 2014-10-01 | custom_distribution 2017-01-07 (current) | ||
| Line 5: | Line 5: | ||
| ===== Creating Custom Installer ===== | ===== Creating Custom Installer ===== | ||
| - | WinSCP uses [[&url(innosetup)|Inno Setup]] as installer. The most simple InnoSetup script for WinSCP may look like the one below. For full WinSCP install script see file ''deployment/winscpsetup.iss'' in the source code. | + | WinSCP uses [[&url(innosetup)|Inno Setup]] as installer. The most simple Inno Setup script for WinSCP may look like the one below. For full WinSCP install script see file ''deployment/winscpsetup.iss'' in the source code. |
| <code iss> | <code iss> | ||
| Line 59: | Line 59: | ||
| </code> | </code> | ||
| - | Save the script into file (e.g. ''winscpsetup.iss''), put files ''WinSCP.exe'' and ''DragExt.dll'' to the same directory and run InnoSetup compiler: | + | Save the script into file (e.g. ''winscpsetup.iss''), put files ''WinSCP.exe'' and ''DragExt.dll'' to the same directory and run Inno Setup compiler: |
| <code> | <code> | ||
| Line 65: | Line 65: | ||
| </code> | </code> | ||
| - | ===== Preconfigured Site ===== | + | ===== [[preconfigured_site]] Preconfigured Site ===== |
| You may have the installer pre-configure [[session_configuration#site|sites]], to make it easier for your users to connect to your server. | You may have the installer pre-configure [[session_configuration#site|sites]], to make it easier for your users to connect to your server. | ||
| Line 85: | Line 85: | ||
| </code> | </code> | ||
| - | ===== Using INI File as Configuration Storage ===== | + | ===== [[ini]] Using INI File as Configuration Storage ===== |
| Instead of modifying the registry from install script you can make the installer create [[config|configuration INI file]]. | Instead of modifying the registry from install script you can make the installer create [[config|configuration INI file]]. | ||
| Line 101: | Line 101: | ||
| </code> | </code> | ||
| - | ===== Distributing Passwords ===== | + | ===== [[distributing_passwords]] Distributing Passwords ===== |
| While not recommended, you can distribute even session passwords. By default the password needs to be stored in encrypted form to option ''Password''. You can store the password from GUI to get the correct encrypted form (note that key for encryption is hostname and username, so the encrypted password cannot be misused for other session). | While not recommended, you can distribute even session passwords. By default the password needs to be stored in encrypted form to option ''Password''. You can store the password from GUI to get the correct encrypted form (note that key for encryption is hostname and username, so the encrypted password cannot be misused for other session). | ||
| If you need to store the password in plain-text, use session option ''PasswordPlain'', instead of ''Password''. Note that WinSCP will, if possible, replace the ''PasswordPlain'' with equivalent ''Password'' option on the first start-up. The same way, you can use ''TunnelPasswordPlain'' instead of ''TunnelPassword'' and ''ProxyPassword'' instead of ''ProxyPasswordEnc''. | If you need to store the password in plain-text, use session option ''PasswordPlain'', instead of ''Password''. Note that WinSCP will, if possible, replace the ''PasswordPlain'' with equivalent ''Password'' option on the first start-up. The same way, you can use ''TunnelPasswordPlain'' instead of ''TunnelPassword'' and ''ProxyPassword'' instead of ''ProxyPasswordEnc''. | ||
| - | ===== Embedded Settings ===== | + | ===== [[embedded_settings]] Embedded Settings ===== |
| As alternative to own installer you can directly embed site settings to WinSCP executable. | As alternative to own installer you can directly embed site settings to WinSCP executable. | ||
| Line 122: | Line 122: | ||
| You can also embed [[public_key#private|private key]] to be used for authentication to ''RCData'' resource named "WINSCP_KEY". WinSCP will automatically try to use it for authentication unless session has its own key configured. | You can also embed [[public_key#private|private key]] to be used for authentication to ''RCData'' resource named "WINSCP_KEY". WinSCP will automatically try to use it for authentication unless session has its own key configured. | ||
| - | To embed ''RCData'' resource you can use any resource editor, for example [[http://www.users.on.net/johnson/resourcehacker/|Resource Hacker]]. Note that the portable executable is compressed, so you may have troubles editing it. Use the application which comes as part of an installation package. | + | ==== Using Resource Hacker ==== |
| + | |||
| + | To embed the ''RCData'' resource you can use any resource editor, for example [[http://www.angusj.com/resourcehacker/|Resource Hacker]]. | ||
| + | |||
| + | Using a command-line interface of the Resource Hacker, you add the "WINSCP_SESSION" resource like: | ||
| + | |||
| + | <code batch> | ||
| + | ResourceHacker.exe -addoverwrite WinSCP.exe, WinSCP.exe, session.ini, RCDATA, WINSCP_SESSION, 0 | ||
| + | </code> | ||
| + | |||
| + | where the ''session.ini'' is the INI file with your session. | ||
| + | |||
| + | Check the generated ''ResourceHacker.log'' for results of the operation. | ||
| + | |||
| + | You can of course also use a GUI interface | ||
| ===== Administration Tasks ===== | ===== Administration Tasks ===== | ||