Technical and distribution information
General
The wodSSH component has two versions (both included in the package):
wodSSHCom is a COM object (wodSSH.dll), designed to be initialized dynamically from your code and declared from within your code. It does not have a user interface, it is windowless. Usually, you will initialize it with
Dim WithEvents Ssh1 as wodSSHCom
and wodSSH is an ActiveX control (wodSSH.ocx) - designed to be put on your application's forms using drag&drop from the control toolbox. Once you put it on the form, no special code is required to initialize it, as your environment (usually VB) will handle it. It has its own explorer-like user interface.
Unlike ActiveX controls, which are licensed the moment you put them on the form (if you have a licensed version of wodSSH, of course), COM object licensing is not directly supported by any container. Therefore you need to add one more line to your code to license wodSSH correctly:
Ssh1.LicenseKey = "put.your.key.here"
| COM Object information |
| Filename | wodSSH.DLL (wodSSH64.DLL for x64) |
| Class name | WeOnlyDo.wodSSHCom.1 |
| Class ID | {20F48DF6-40B7-4069-8FFD-0627F8F8356E} |
| Events class ID | {0x0BA7D89D,0x1545,0x4FE9,{0xB4,0xA3,0x95,0x9B,0x25,0xF8,0x71,0x43}} |
| Compatibility | VB 5.0 and above, VFP 5.0 and above |
| Built with | Microsoft Visual Studio 2008 C++, OpenSSL |
| Required DLLs | None required, wodKeys.dll optional, only if Key generation/loading/saving is used. |
| ActiveX Control information |
| Filename | wodSSH.OCX (wodSSH64.OCX for x64) |
| Class name | WeOnlyDo.wodSSH.1 |
| Class ID | {09F5B964-C8BF-4E9B-A9DB-BCE93151FE1E} |
| Events class ID | {0xB53615C5,0x468A,0x41E0,{0x8F,0x42,0x2D,0xC3,0x8C,0xC8,0x5F,0x17}} |
| Compatibility | VB 5.0 and above, VFP 5.0 and above |
| Built with | Microsoft Visual Studio 2008 C++, OpenSSL |
| Required DLLs | None required, wodKeys.dll optional, only if private keys are used. |
| Interfaces |
| IwodSSHNotify | {1AEF7312-C928-4034-BF04-1E0F773A391D} |
| Documentation |
| Help filename | wodSSH.CHM |
Distribution note
When you develop and distribute an application that uses this component:
- Choose whether to include the COM object (wodSSH.DLL/wodSSH64.DLL) or the ActiveX control (wodSSH.OCX/wodSSH64.OCX) into the installation package. The COM object and the ActiveX control are independent on each other.
- You should include wodKeys.DLL/wodKeys64.DLL for Key management - if it is needed in your application. wodSSH does not depend on it, it only uses it for client authentication with the private key.
- Above binaries can be included royalty-free in your application.
- Use RegSvr32.EXE (or any other installer package creator) to register both the OCX and the DLL. Usually, installer software will do this for you
- Install the component file(s) into the user's Windows SYSTEM32 folder. The component file(s) has/have version information built into it. So, during installation, you should ensure that you are not overwriting a newer version.
Using licensed version
To use the retail (licensed) version in your code, put your license key into LicenseKey property, immediately after initializing the component. For the ActiveX control, you cannot do this (there is no LicenseKey property) because your license key will be read internally by wodSSH.
Platforms
Windows
Back to product page