Standards and platform support

100% managed .NET code with no external dependencies #

  • Rebex HTTPS is written in 100% managed C# code.
  • No external dependencies. It only needs Windows and .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 HTTPS supports the following .NET Framework 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)

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

Rebex HTTPS 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 HTTPS on these operating systems.

.NET Core #

Rebex HTTPS supports .NET Core platform.

Supported frameworks:

  • .NET Core 1.1
  • .NET Core 2.0

Supported operating systems:

  • Windows 10
  • Windows 8.1
  • Windows 7 (SP1 and higher)
  • Windows Server 2008 R2 (SP1 and higher)

Operating systems with experimental support:

  • macOS (64-bit)
  • Linux (64-bit)

.NET Standard #

Rebex HTTPS supports .NET Standard 1.5, 1.6 and 2.0 on .NET Core 1.1 and 2.0. Support for .NET Standard on .NET Framework 4.6.x is experimental.

Mono on Linux #

Rebex HTTPS supports Mono version 3.x, 4.x on Linux and Apple macOS (OS X).

.NET Compact Framework on handhelds and mobiles #

Rebex HTTPS supports Microsoft legacy 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 as part of extended legacy platform support.
Contact sales@rebex.net for details (see also Legacy platform support).

Supported mobile operating systems:

  • Windows CE 5.0, 6.x
  • Pocket PC
  • Windows Mobile
  • Windows Embedded Compact 7
  • 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 HTTPS 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 HTTPS for Universal Windows Platform is included in the installation package.

Supported platforms:

  • Windows 10 Store Apps
  • Windows 10 Mobile
  • Windows 10 IoT

ASP.NET #

Rebex HTTPS 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, multi-threaded, it may be limited by MediumTrust security level...).

Further info on using Rebex components in web environment can be found in How to use Rebex SFTP or FTP/SSL in ASP.NET knowledge base article. The article discusses SFTP and FTP/SSL, but implications for Rebex HTTPS component are the same.

Legacy platform support #

Legacy version of Rebex HTTPS for .NET Compact Framework 2.0 is still available as part of extended legacy platform support. Contact sales@rebex.net for details.

See also How long will Rebex support old versions of .NET Framework knowledge base article.

Internet RFC specifications #

Implemented HTTP RFC:

Implemented TLS RFC:

Other RFC:

Please note that some non-essential features might not be supported. Let us know if you need to add anything.

FIPS 140-2 mode #

Rebex HTTPS 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.

Proxy servers #

  • 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 HTTPS.

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)
  • Blowfish
  • CTR and CBC block cipher modes
  • MD5
  • SHA-1
  • SHA-2 (SHA-256, SHA-384, SHA-512)

Learn more about TLS/SSL security standards details.

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 HTTPS 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 HTTPS in SSIS, SQL CLR and PowerShell environments.

Authentication methods #

  • Basic
  • NTLM
  • Negotiate (not supported on Mono, Android and iOS)
  • Kerberos v5 (not supported on Mono, Android and iOS)

Single sign-on authentication is supported for NTLM, Negotiate, Kerberos.

See more about authentication.

Other technologies #

  • IPv4 and IPv6 support