INFO: Using multiple Rebex components in a single project

When using multiple Rebex components in a single project (such as Rebex SFTP with Rebex Secure Mail, but any combination is possible), make sure all the components belong to the same release (such as 2017 R1).

Referencing different versions of Rebex components from a single assembly is not supported. This means - for example - that it's not possible to use Rebex SFTP 2017 R1 alongside Rebex Secure Mail 2012 R2 within a single project.

Background

All Rebex components reference Rebex.Common.dll and some reference Rebex.Networking.dll as well. When referencing multiple versions of different Rebex components, this creates a conflict. To solve this, make sure that only assemblies from the same release (such as 2015 R1) are used alongside each other - these are guaranteed to be compatible.

Example - different version of SFTP and Secure Mail

Let's consider following example. User has a license for following components:

  • Rebex Mail version 2012 R2 (outdated version)
  • Rebex SFTP version 2018 R1 (recent version)

What are your options?

Option 1: Upgrade both components to the current version

Pros

  • Both components are the same version and can be used in the same application.
  • Support for up-to-date security standards in both components.
  • Recent versions of both components are supported by Rebex.

Cons

  • Having to renew the outdated component.
  • The need to renew support for both component in future to keep both versions in sync.

Option 2: Upgrade to Rebex Total Pack

Upgrade to Total Pack and get access to the current version of all Rebex components.

Pros

  • Both components are the same version and can be used in the same application.
  • Support for up-to-date security standards in both components.
  • Recent versions of both components are supported by Rebex.
  • Get all Rebex components in one package. No problems with different versions in the future.

Cons

  • The need to upgrade to Rebex Total Pack, which might be more expensive than option 1. However, when consolidating more than two components, this is often the cheaper option. Contact sales@rebex.net for assistance.

Option 3: Downgrade both components to an outdated version

Use the same old version of both components. For example Rebex SFTP 2012 R2 and Rebex Secure Mail 2012 R2. This is strongly discouraged.

Pros

  • No additional costs if you don't need any support. You already have access to old binaries for both components.

Cons

  • No recent bugfixes and enhancements.
  • Oudated security. Old versions may not support latest encryption ciphers and they might enable weak or vulnerable algorithms by default. You might already be unable to connect to servers that require up-to-date encryption.
  • When you need support later, or when your server drops support for old encryption algorithms, you may have to renew the support contract for both components anyway.
  • Limited support from Rebex. If you renew your support contract, we will do our best to support you. However, with the outdated version, our options might be limited. We don't backport bugfixes and enhancements unless a special agreement has been negotiated.