FlowSsh: SSH client library for C, C++ and .NET
The same SSH library as we use in our SSH server for Windows is available for licensing for SSH client applications.
- Separate easy to use interfaces for C, C++, and .NET.
- Fully documented.
- Comes with several complete sample applications in C, C++, C#, and Visual Basic.
- Full support for public key authentication.
- Full support for SFTP and tunneling / port forwarding.
- Support for general channel types, including exec requests and terminal sessions. (Terminal emulation not included.)
- Supports ZLIB compression. (But does not use the widely used zlib library.)
- Supports connecting through a proxy.
- When FIPS is enabled in Windows, uses Windows built-in cryptography, validated by NIST to FIPS 140-2 under certificates #1892, #2357, and #2606. On Windows XP and 2003, uses the Crypto++ 5.3.0 FIPS DLL, originally validated by NIST under certificate #819 (historical). When Windows cryptography is used, but FIPS mode is not enabled in Windows, additional algorithms may be available.
- Pluggable cryptographic interface allows substituting a different cryptographic module.
- Compatible with both 32-bit and 64-bit Windows applications. (Non-Windows platforms not supported.)
- Code base separate and independent of other SSH implementations.
- Does not contain parts subject to GPL or similar licenses.
Included in Bitvise SSH Client
Since Bitvise SSH Client version 6.41, FlowSshNet is included with our SSH Client, and can be used under the Bitvise SSH Client license on computers where the Client is installed. PowerShell scripts are included under the SSH Client installation directory, demonstrating how to use FlowSshNet with PowerShell.
For use independent of Bitvise SSH Client, FlowSsh 7.31 is available for download. Build instructions and license terms are included in the archive.
Use of FlowSsh for evaluation and testing is free of charge. To include FlowSsh in your production application, contact us.
When used without a license, FlowSsh will display an evaluation dialog unless Bitvise SSH Client is also installed. To avoid the evaluation dialog during testing, install Bitvise SSH Client.
Complete FlowSsh documentation can be found here.
FlowSsh is available in the following license types:
A per-developer license costs USD 599.95 per developer. It is valid for any number of programs and applications, but requires a fee for each developer involved in writing programs that use FlowSsh.
A per-application license costs USD 1,500 per application. It is valid for a single, specific application, but permits use by an unlimited number of developers.
A full source code license costs USD 5,000. It permits modification of source code, and use in multiple products. It allows use of the inner FlowSsh library in server applications, which the outer FlowSshC, C++, and .NET wrappers do not. However, it does not permit distribution of FlowSsh source code, or use in general-purpose SSH products, competing with Bitvise's.
There are no royalty fees based on use of the resulting applications. Use in commercial programs is permitted and encouraged.
Each license type comes with 12 months of free access to new versions of FlowSsh. Subsequently, upgrade access extension is optional, and is available at 20% of the license price per year. Like with our other licenses, upgrade access years cannot be skipped, but there are also no penalties for retroactive upgrade access extension.
To purchase a license, please contact us.
In our current design, FlowSsh is incompatible with applications that use .NET Application Domains. The FlowSsh implementation makes heavy use of fibers, which .NET Application Domains do not support. This means FlowSsh is currently not a suitable choice for use in ASP.NET (within an IIS process).
Bug reports, suggestions, and specific questions to which direct responses are possible are handled free of charge. Please contact us if you would like to suggest a feature or report an issue.
In-depth support to help you use FlowSsh, or any other of our products, is available at USD 399.95 per incident.