Technical and distribution information

General

The wodSSHTunnel component has three versions (all included in the package):

1. wodTunnelCom is an in-process COM object (or ActiveX DLL) called wodTunnel.dll, which is designed to be declared and initialized dynamically from your code. It does not have a user interface, it is windowless. Usually, you will initialize it with



2. wodTunnel is an ActiveX control (called wodTunnel.ocx), which is designed to be put on an 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 perform the necessary initialization.

3. wodSSHTunnel is an out of process COM object (or ActiveX EXE) called wodTunnel.exe, which is designed to act as standalone (out of process) executable that can work in separate process, thus being unaffected by various blocking functions/components you may use in your applications. A typical example is database driver clients that block the main application when you try to connect it through wodSSHTunnel. The DLL and OCX may hang because of this - the thread gets blocked by the Database component and they cannot process socket events. The External executable isn't affected by this.

COM object licensing is not directly supported by any container. Unlike ActiveX controls which are licensed the moment you put them on the form (if you have a licensed version of wodTunnel, that is), you need to add an additional line to your code in order to license wodTunnel correctly:

COM Object information
Filename	wodTunnel.DLL (wodTunnel64.DLL for x64)
Class name	WeOnlyDo.wodTunnelCom.1
Class ID	{A9982900-33C1-40E0-8A65-7A5DE9A7BABC}
Events class ID	{0xE126FA79,0xED5E,0x4BE9,{0xB4,0x48,0x56,0x31,0xFF,0xDF,0x52,0xD3}}
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 EXE information
Filename	wodTunnel.EXE (wodTunnel64.EXE for x64)
Class name	WeOnlyDo.wodTunnelServ.1
Class ID	{EA470BDB-611A-4B73-A759-1953C5E537E6}
Events class ID	{0xA5058F2E,0xE0B7,0x4698,{0xB0,0x62,0x8A,0x8A,0xD4,0xE6,0x6A,0x83}}
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	wodTunnel.OCX (wodTunnel64.OCX for x64)
Class name	WeOnlyDo.wodTunnel.1
Class ID	{A2AAD48E-67E5-448E-A889-D60E7F642DBD}
Events class ID	{0x30AEFF49,0x5274,0x44A3,{0x86,0x4C,0xB6,0x97,0x8F,0x06,0xE9,0xD0}}
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.

Interfaces
IChannel	{3138A881-7C8F-4E66-8909-7DDA49DBA369}
IChannels	{1068E3E0-2F70-4511-819F-0AC295AF9658}
IUser	{C0EFE834-8098-4390-95C9-18E1D936BF5C}
IUsers	{EDE028FC-20F9-43F3-B21C-17F84A4828DF}
IwodTunnelNotify	{77D2A849-7A0A-4cee-BA8C-B889CD830DB0}

Documentation
Help filename	wodTunnel.CHM/td>

Distribution note

When you develop and distribute an application that uses this component:

1. Choose between the in-process COM object (wodTunnel.DLL/wodTunnel64.DLL), the ActiveX control (wodTunnel.OCX/wodTunnel64.OCX) and the out-of-process COM Object (wodTunnel.EXE/wodTunnel64.EXE) to include into the installation package. All versions are independent on each other.

2. You should include wodKeys.DLL/wodKeys64.DLL for Key management - if it is needed in your application. wodTunnel does not depend on it, it only uses it for client authentication using private keys.

3. The above binaries can be included in your applications royalty-free.

4. Use RegSvr32.EXE (or any other installer package creator) to register both the OCX and the DLL. Your installer software will usually do this for you. To register the EXE you will need to run it on the target system with a special parameter, as follows:

wodTunnel.exe /RegServer

5. Install the component file(s) into the user's Windows SYSTEM32 folder. The component file(s) have version information built into them, so during installation you should ensure that you are not overwriting a newer version of the same file.


Using the licensed version

To use the retail (licensed) version of the COM objects in your code, put your license key into the LicenseKey property immediately after initializing the component. For the ActiveX control, you cannot do this (and there is no LicenseKey property) because your license key will be loaded internally by wodTunnel.OCX.

Platforms

Windows