Back to product page
- Introduction
- Overview
- License Agrement
- Getting Started
- Objects
- Enumerations
- wodSSH
- Methods
- Properties
- AllocatePty
- Authentication
- Blocking
- ClientName
- Columns
- Command
- Compression
- DataOut
- DataReady
- Encoding
- Encryption
- EncryptionList
- ErrorText
- ExitSignal
- ExitStatus
- FIPS
- ForwardHost
- ForwardPort
- HMacList
- Hostname
- KeepAlives
- KeyExchangeList
- KeyForward
- KeySignatureList
- LastError
- Login
- MyHostname
- MyIP
- Notification
- Password
- Port
- PrivateKey
- Prompt
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RemoteIdentification
- Rows
- ShowStdErrorMessages
- State
- StateText
- StripANSI
- StripNull
- Subsystem
- TerminalSpeed
- TerminalType
- Timeout
- UseIPv6
- Version
- Events
- IwodSSHNotify
- How to get support?
- Technical information
- Fast notifications interface
- Error list
SSH Client Introduction
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 the Telnet protocol, with negotiation of telnet options
- windowless, you can use wodSSH in unattended mode
- internal compression - user defined level 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 the 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 are transparent for the end-user but provide a secure layer on which data is transmitted. So your passwords are not exposed on the Internet. There is also an option to secure your data using the SSL protocol instead (check out wodTelnetDLX!), but sometimes SSL is too much hassle - 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, 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 a remote server is based on the SSH1 or SSH2 protocol version and then communicate accordingly. It will provide you with information about the remote server Fingerprint, so you can always get authenticated information about the remote server.ASP, VB, VC, VBS - one component fits all....
wodSSH can be used as scripting client. You can easily set it up to connect to a server, execute one or more commands, wait for a response, and disconnect, all of it fully automated. It also supports blocking and non-blocking operations, thus it is suitable for many environments, such as ASP. Since version 1.0.2.2 wodSSH has had a feature similar to the UNIX "expect" facility - it allows you to use the WaitFor and Execute commands to easily execute several commands in a row, waiting for each one to finish and acting according to the results.When you're unsure of when to send the actual command, wodSSH can help. Using its unique Prompt property, it can fire an event whenever the remote server sends the command prompt to enter a new command. All you have to do is send your new command once this event is fired.
Authentication - select between login/password and login/publickey.. Or use both..
Since version 1.0.1.1 wodSSH has also supported public key authentication (only for the 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 into the server's authorization files in the required format.Proxy support
wodSSH supports SOCKS4/5 proxies and tunnels through WEB proxy servers (using the CONNECT command). You can use your favorite proxy server to access the internet.Wait no more - communicate securely. Check out wodSSH.