Back to product page
- Introduction
- Overview
- License agreement
- Getting Started
- Objects
- Enumerations
- wodSSHD
- Methods
- Properties
- Events
- Connecting
- CryptoInformation
- Disconnected
- LoginGSSAPI
- LoginPassword
- LoginPubkey
- PortBindRequest
- PortForwardConnect
- PortForwardDisconnect
- PortForwardRequest
- Received
- ServiceRequest
- ServiceStart
- SftpDeleteFile
- SftpDownloadFile
- SftpFileTransferData
- SftpListDir
- SftpListDirData
- SftpMakeDir
- SftpProgress
- SftpRemoveDir
- SftpRename
- SftpTransferComplete
- SftpUploadFile
- StateChanged
- IwodSSHDNotify
- Methods
- Connecting
- CryptoInformation
- Disconnected
- LoginGSSAPI
- LoginPassword
- LoginPubkey
- PortBindRequest
- PortForwardConnect
- PortForwardDisconnect
- PortForwardRequest
- Received
- ServiceRequest
- ServiceStart
- SftpDeleteFile
- SftpDownloadFile
- SftpFileTransferData
- SftpListDir
- SftpListDirData
- SftpMakeDir
- SftpProgress
- SftpRemoveDir
- SftpRename
- SftpTransferComplete
- SftpUploadFile
- StateChanged
- Methods
- SSHKeyPair
- SSHUser
- SSHUsers
- How to get support
- Technical information
- Fast notifications
- Error list
Technical and distribution information
General
wodSSHServer component has two versions (both included in the package):wwodSSHDCom is a COM object (wodSSHD.dll), designed to be initialized dynamically from your code, and declared from within your code. It does not have user interface, it is windowless. Usually, you will initialize it with
Dim WithEvents Sshd1 as wodSSHDCom
and wodSSHD as ActiveX control (wodSSHD.ocx) - designed to be put on application's form using drag&drop from control toolbox. Once you put it on the form, no special code is required to initialize it, since your environment (usually VB) will handle it. It has it's own explorer-alike user interface.
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 licensed version of wodSSHServer, of course), you need one more line to put in your code to license wodSSHServer correctly:
Sshd1.LicenseKey = "put.your.key.here"
COM Object information | |
---|---|
Filename | wodSSHD.DLL (wodSSHD64.DLL for x64) |
Class name | WeOnlyDo.wodSSHDCom.1 |
Class ID | {B1ACEA20-274F-4DE0-AEC6-BBD3DD88D0E0} |
Events class ID | {0x221A3E44,0x2F0F,0x4302,{0x83,0xB2,0xDC,0x3A,0xAA,0x3C,0x03,0x72}} |
Compatibility | VB 5.0 and above, VFP 5.0 and above |
Built with | Microsoft Visual Studio 2008 C++, OpenSSL |
Required DLLs | None required. |
ActiveX Control information | |
---|---|
Filename | wodSSHD.OCX (wodSSHD64.OCX) |
Class name | WeOnlyDo.wodSSHD.1 |
Class ID | {0363FD15-C2B0-40FE-AF60-F3292307819F} |
Events class ID | {0xE9D68814,0x84A7,0x405A,{0xB2,0x49,0xEC,0x62,0xB0,0xE7,0x29,0x2A}} |
Compatibility | VB 5.0 and above, VFP 5.0 and above |
Built with | Microsoft Visual Studio 2008 C++, OpenSSL |
Required DLLs | None required. |
Interfaces | |
---|---|
IBlob | {0B7B28FE-1BE1-4b3b-B289-BA783EE06F43} |
IFileBlob | {51732A8D-F34E-4396-BE27-506ED89765B4} |
IMemBlob | {388F9A64-FBC8-480D-A81F-A470CD36732D} |
IStreamBlob | {67E6EF70-CA03-4950-B08A-0AA2FF1B5572} |
Documentation | |
---|---|
Help filename | wodSSHD.CHM |
- Choose between COM object (wodSSHD.DLL/wodSSHD64.DLL) and the ActiveX control (wodSSHD.OCX/wodSSHD64.OCX) to include into the installation package. Both versions are independent on each other.
- 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.