wodSSH.NET component
SSH Component (C#, VB.NET) for .NET, SSH Library, Rlogin and Telnet component for .NET

Client side .NET component for SSH, Telnet and Rlogin protocols 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-alike behavior model Regular expressions can be used to easily match remote prompt Fully managed - source in C# available Available as x86 and x64 binaries Samples in VB.NET, C#

	Pricing - per developer seat 1 Developer license $199.00 Add to cart 3 Developer Team licenses (15% off) $507.45 Add to cart 1 Developer license with source code $359.00 Add 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.NET is a client component for C# and VB.NET and provides support for communication with remote console-type services. It allows you to communicate SSH encrypted (and secured, of course) with SSH1 and SSH2 (secure-shell) servers, as well to Telnet servers (using Telnet or Rlogin protocols that are NOT encrypted). 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.

How to use it? Using wodSSH.NET is easily - just put it on your form (or initialize new instance on the fly), set Protocol type and issue Connect method - and just wait for things to happen. You connect to SSH servers, which are standard today in remote console communication. wodSSH.NET 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.

Can be used also in scripting environments wodSSH.NET 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's suitable for many environments, such as ASPX. When you're unsure when to send actual command, wodSSH.NET 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. Wait no more - communicate securely. Check out wodSSH.NET.

Example of use [Visual Basic] Dim WithEvents Ssh1 As WeOnlyDo.Client.SSH Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) _             Handles MyBase.Load   Ssh1 = New WeOnlyDo.Client.SSH() ' Initialize new instance   Ssh1.Login = "your login" ' Set your login/username   Ssh1.Password = "your password" ' Set your password   Ssh1.Encryption = WeOnlyDo.Client.SSH.EncryptionMethods.Auto ' Any encryption is ok   Ssh1.Protocol = SSH1 ' Set SSH version   Ssh1.Command = "ls -al" & Chr(10) ' Define command which we'll send to the server   Ssh1.Connect("your.host.com") ' Connect, finally. Now wait for Connected event to occur End Sub [C#] using WeOnlyDo.Client; SSH Ssh1; private void Form1_Load(object sender, System.EventArgs e) {   Ssh1 = new SSH(); // Initialize new instance   Ssh1.ConnectedEvent += new WeOnlyDo.Client.SSH.ConnectedDelegate(Ssh1_Connected);           // defined somewhere in the code   Ssh1.Login = "your login"; // Set your login/username   Ssh1.Password = "your password"; // Set your password   Ssh1.Encryption = WeOnlyDo.Client.SSH.EncryptionMethods.Auto; // Any encryption is ok   Ssh1.Protocol = SSH1; // Set SSH version   Ssh1.Command = "ls -al "; // Define command which we'll send to the server   Ssh1.Connect(TextBox2.Text); // Connect, finally. Now wait for Ssh1_Connected event to occur }