Version 2019 R3.1: Removed SSL 3.0 from TlsVersion.Any

This is an enhancement and bugfix release:

Removed SSL 3.0 from TlsVersion.Any

Even though we disabled SSL 3.0 by default in all our components almost five years ago, an SSL30 enum value was still included in TlsVersion.Any (along with TLS10, TLS11 and TLS12), which means some users could have been using it by mistake. Unfortunately, that would be a security issue because SSL 3.0 (a predecessor to TLS 1.0 protocol published in 1996) is comprehensively broken and should no longer be used any more. Application that still use it violate RFC 7568, which deprecated SSL 3.0 in 2015. If you are using TlsVersion.Any with an older version of Rebex libraries, please consider replacing it with TlsVersion.TLS12 | TlsVersion.TLS11 | TlsVersion.TLS10. We have still not removed SSL 3.0 support because some of our customers still rely on it, but we strongly advise everyone to upgrade as soon as possible. Additionally, due to the forthcoming deprecation of TLS 1.0 and 1.1, consider only enabling TLS 1.2 if your servers already support it.

Serialization on Xamarin.Android and Xamarin.iOS platforms

Classic .NET serialization ([Serializable] atrributes and related infrastructure) is now supported on Xamarin.Android and Xamarin.iOS platforms.

Enhanced compatibility with Pure-FTPd server

Rebex FTP/SSL includes several new workarounds that enhance compatibility with Pure-FTPd server.

And more...

See the release history for a complete list of changes.

End of Standard Support for .NET Compact Framework 3.5 and 3.9

2019 R3.1 no longer includes support for .NET Compact Framework 3.5/3.9 in the standard package. If you use this legacy platform, please check out End of Standard Support for .NET Compact Framework 3.5 and 3.9 to learn more.