SSH ActiveX component

SSH ActiveX Client OCX/DLL, SSH Component for Windows



 
  • Client side ActiveX component for Telnet and SSH protocol
  • Encryption with AES, DES, 3DES or BLOWFISH ciphers
  • Uses FIPS 140-2 certified OpenSSL crypto library
  • Can work in async environment, but also in blocking mode
  • Authenticate with private key or password
  • Compression - from 0 up to level 9
  • Unix Expect-like behavior model
  • Regular expressions can be used to easily match remote prompt
  • Installation contains x86 and x64 binaries
  • Samples in Visual Basic, VC, Delphi, HTML

Pricing - per developer seat
1 Developer license$189.00Add to cart
3 Developer Team licenses (15% off)$481.95Add to cart
1 Developer license with source code$349.00Add to cart
Each license includes one year of free updates, and unlimited lifetime technical support. Remember that each developer must have his own design-time license.


General information

wodSSH is windowless (SSH client and Telnet client) component that provides support for communication with remote console-type services. The SSH transport layer is a secure, low level transport protocol which provides strong encryption, cryptographic host authentication and integrity protection. Most commonly wodSSH will be used for Telnet based servers (running on UNIX OS), but wodSSH does even more: it allows you to carry out encrypted (and therefore secured) communication with SSH1 and SSH2 (secure-shell) servers, as well as any other non-encrypted server (such as SMTP or POP3).

Features include:

  • support for both SSH1 and SSH2 protocols
  • support for Telnet protocol, with negotiation to telnet options
  • windowless, you can use wodSSH in unattended mode
  • internal user defined level compression - from 0 (no compression) to 9 (highest compression)
  • proxy support
  • fast notifications - you can use callback methods instead of slow events
  • blocking support (for scripting environments) and asynchronous (state driven) model
  • Prompt event - fired when a command prompt is found in received data
  • WaitFor and Execute methods - approach similar to UNIX "expect" command
  • Password and PrivateKey authentication
  • Port forwarding through one channel

Don't use insecure Telnet - use SSH instead

The Telnet protocol is widely used for character-based communication. Due to its insecurity, most sys admins use SSH protocols instead - they're transparent for the end-user, but provide a secure layer on which data is transmitted, so your passwords are not exposed on the internet.

You might want to consider securing your data using the SSL protocol instead (check out wodTelnetDLX!), but sometimes SSL brings too many hassles - you need to buy certificates sign them, etc.. SSH doesn't need any of this.

How to use it?

Using wodSSH is easy - just put it on your form, set the Protocol type and issue the Connect method - and just wait for things to happen.

When in secure mode you can connect to SSH servers, which are standard today in remote console communication. wodSSH is able to automatically determine if the remote server is based on SSH1 or SSH2 protocol version and communicate accordingly. It will provide you with information about the remote server's Fingerprint, so you can always get authenticated information about remote server.

ASP, VB, VC, VBS - one fits all...

wodSSH can be used as scripting client. You can easily set it up to connect to server, execute one or more commands, wait for a response and just disconnect - all of it fully automated. It also supports blocking and non-blocking operations, thus it's suitable for many environments, such as ASP.
wodSSH has also supported a UNIX "expect"-like feature - use WaitFor and Execute commands to easily execute several commands in a row, waiting each one to finish and provide you with some results. When you're unsure when to send the actual command, wodSSH can help. Using its unique Prompt property, it can fire an event for you whenever the remote server sends a prompt to enter a new command. All you have to do is send a new command once this event is fired.

Authentication - select between login/password and login/publickey

Or use both! wodSSH has also supports public key authentication (only for SSH2 protocol!). Dealing with keys is easy - we have included a Keys object that will allow you to generate, load, and save keys and pass them to wodSSH. This way you can easily use your private key to authenticate with the server. The Keys object will also generate public key data that should be pasted directly on the server's authorization files in the required format.

Proxy support

wodSSH support SOCKS4/5 proxies, as well tunnels through WEB proxy servers (using CONNECT command). You can use your favorite proxy server to access the Internet.

Licensing

Upon purchase, you have the right to distribute wodSSH.DLL, wodSSH.OCX and wodKeys.DLL binaries in your applications free of charge. To license your existing versions (not DEMO version!), in the DLL version use the LicenseKey property with the key you receive from us. In the OCX version you don't need to setup your key, it will be handled by your programming environment.

Wait no more - communicate securely. Check out wodSSH.

Additional notes

wodKeys component is included in our setup package free of charge. It can be used for private key management - to Generate new keys, Load/Save the, obtain public keys etc.. the helpfile can be found here.



Now shipping version
  3.0.1


Back to wodSSH home
View wodSSH release notes
Download wodSSH evaluation package
View more wodSSH examples
Browse online Help files
Visit forum
Purchase wodSSH license
Purchase wodSSH 3 licenses pack (15% off)
Purchase wodSSH source code license

>