Client component that provides support for communication with remote console-type services.Most commonly, it will be used for Telnet based servers (running on UNIX OS), but wodSSH does even more: it allows you to communicate encrypted (and secured, of course) with SSH1 and SSH2 (secure-shell) servers, as well as any other non-encrypted server (such as SMTP or POP3).For ones that don't know - the SSH transport layer is a secure low level transport protocol. It provides strong encryption, cryptographic host authentication, and integrity protection.Using wodSSH is easily - just put it on your form, set Protocol type and issue 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 remote server is based on SSH1 or SSH2 protocol version, and communicate accordingly. It will provide you with information about remote server Fingerprint, so you can always get authenticated information about remote server.

wodSSH can be used as scripting client. Easily, you can set it up to connect to server, execute one or more commands, wait for response, and just disconnect. And all of it fully automated. It also supports blocking and non-blocking operations, thus it's suitable for many environments, such as ASP. Using WaitFor and Execute methods, it will behave just like expect command known from UNIX systems.

When you're unsure when to send actual command, wodSSH may help also. Using it's unique Prompt property, it can fire event for you whenever remote server sent command prompt to enter new command. All you have to do is send new command once this event is fired.

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