Standards and platform support
100% managed .NET code with no external dependencies #
- Rebex FTP/SSL is written in 100% managed C# code.
- No external dependencies. It only needs .NET Framework.
- No open source code used.
- Fully CLS-compliant.
- Supports any .NET language (C#, VB.NET, C++/CLI, etc.)
- Platform-independent code. Same assemblies for both 32-bit and 64-bit applications.
- Complete source code available.
.NET Framework on Windows #
Rebex FTP/SSL supports the following platforms:
- .NET Framework 4.7
- .NET Framework 4.6.x
- .NET Framework 4.5.x
- .NET Framework 4.0
- .NET Framework 3.5
- .NET Framework 3.0
- .NET Framework 2.0
- Both 32-bit and 64-bit versions (same DLLs)
Legacy binaries for .NET Framework 1.0 and 1.1 are available for registered customers.
For details, see legacy platform support section.
Supported IDE versions:
- Microsoft Visual Studio 2008
- Microsoft Visual Studio 2010
- Microsoft Visual Studio 2012
- Microsoft Visual Studio 2013
- Microsoft Visual Studio 2015
- Microsoft Visual Studio 2017
Supported Windows versions:
- Windows 10
- Windows 8
- Windows 8.1
- Windows 2012 Server
- Windows 2012 Server R2
- Windows 2008 Server
- Windows 2008 Server R2
- Windows 7
- Windows Vista
Rebex FTP/SSL is known to work on Windows XP SP3 and Windows Server 2003 R2.
However, these platforms already reached end-of-life,
which means we cannot guarantee any kind of support for Rebex FTP/SSL on these operating systems.
Mono on Linux #
Rebex FTP/SSL supports Mono version 3.x, 4.x on Linux and Apple macOS (OS X).
.NET Compact Framework on handhelds and mobiles #
Rebex FTP/SSL for .NET Compact Framework supports several Microsoft handheld and mobile platforms.
Supported frameworks:
- .NET Compact Framework 3.5
- .NET Compact Framework 3.9
Legacy binaries for .NET Compact Framework 2.0 are available for registered customers upon request.
For details, see legacy platform support section.
Supported mobile operating systems:
- Windows CE
- Pocket PC
- Windows Mobile
- Windows Embedded Compact 2013
Supported IDE versions:
- Microsoft Visual Studio 2008
- Microsoft Visual Studio 2012
- Microsoft Visual Studio 2013
Xamarin.iOS #
- Xamarin Studio/Visual Studio with Xamarin.iOS 8.6 or later
- iOS 5.1.1 or later
Xamarin.Android #
- Xamarin Studio/Visual Studio with Xamarin.Android 4 or later
- Android 2.3.3 or later (Android API version 10 or later)
Xamarin.Mac #
Experimental version of Rebex FTP/SSL for Xamarin.Mac is included in the installation package.
Supported projects:
- Xamarin.Mac Mobile
- Xamarin.Mac .NET 4.5 Framework
Requires Xamarin Studio with Xamarin.Mac 2.x or later and OS X 10.7 or later.
Universal Windows Platform #
Experimental version of Rebex FTP/SSL for Universal Windows Platform is included in the installation package.
Supported platforms:
- Windows 10 Store Apps
- Windows 10 Mobile
- Windows 10 IoT
.NET Core #
Experimental version of Rebex FTP/SSL for .NET Core is included in the installation package.
Supported platforms:
- .NET Core
- .NET Standard 1.5 (on .NET 4.6.2 and .NET 4.7)
ASP.NET #
Rebex FTP/SSL can be used within an ASP.NET web page.
However, you have to keep in mind specific features of the ASP.NET platform (it is stateless, multithreaded, it may be limited by MediumTrust security level...).
For more details, see How to use Rebex SFTP or FTP/SSL in ASP.NET knowledge base article or try the FTP client in ASP.NET sample.
Internet RFC specifications #
Implemented (FTP and TLS) RFCs:
Please note that some non-essential features might not be supported. Let us know if you need to add anything.
TLS/SSL versions #
Supported TLS/SSL protocol versions:
- SSL 3.0
- TLS 1.0
- TLS 1.1
- TLS 1.2
FIPS 140-2 mode #
Rebex FTP/SSL can operate in a FIPS 140-2 compliant mode. When enabled, only FIPS-approved
cryptographic modules from MS CryptoAPI are used. FIPS mode is activated automatically when Windows is running in FIPS mode.
To switch on the FIPS mode manually, set
Rebex.Security.Cryptography.CryptoHelper.UseFipsAlgorithmsOnly to true.
Legacy platform support #
Legacy version of Rebex FTP/SSL for .NET Framework 1.0 and 1.1 is still available for registered customers.
However, it's no longer maintained or supported and all customers are advised to upgrade to a more recent platform as soon as possible.
Legacy version of Rebex FTP/SSL for .NET Compact Framework 2.0 is still available for registered customers upon request.
For details, see How long will Rebex support old versions of .NET Framework
knowledge base article.
Directory listing formats #
Rebex FTP/SSL can parse directory listings using the following formats:
- Unix "
ls" (ProFTPd, Wu-FTPd, Microsoft FTP and many others)
- DOS (Microsoft FTP and others)
- Netware
- DJ Bernstein's EPLF
- glFTPd ANSI-colored list
- VMS and MultiNet (both single and multiline)
- IBM 4690
- Tandem Guardian
- support for custom list parsers
Proxy servers #
- Various FTP proxies
- SOCKS4
- SOCKS4a (Socks4 with domain name resolving)
- SOCKS5
- HTTP proxies with CONNECT method support
- Tunneling through SSH servers
Learn how to use proxy servers in Rebex FTP/SSL.
Cryptographic algorithms #
- Diffie-Hellman key exchange
- RSA
- DSA (with support of non-standard key sizes of up to 4096 bits)
- Tripple DES
- ArcFour (compatible with RC4)
- AES (Rijndael)
- SHA-1
- SHA-2 (SHA-256, SHA-384, SHA-512)
- MD5
Learn more about TLS/SSL security standards details.
Certificate and private key formats #
Certificate formats
- PKCS #12
- PFX
- DER (binary or base64 encoded)
- CER (binary or base64 encoded)
External private key formats
- PKCS #8 keys
- OpenSSH/OpenSSL (SSLeay) keys
- PuTTY .ppk keys
Scripting platforms #
Rebex FTP/SSL is designed primary for use in .NET framework applications.
However, it can be used in several other scripting and hosting environments:
- Microsoft SQL Server SSIS packages
- Microsoft SQL Server SQL CLR stored procedures
- Microsoft PowerShell scripts
See how to use Rebex FTP/SSL in SSIS, SQL CLR and PowerShell environments.