[Mono-dev] Status of SslStream and Related Classes

Sebastien Pouliot sebastien.pouliot at gmail.com
Thu Aug 11 22:39:07 EDT 2005

Hello JD,

On Thu, 2005-11-08 at 13:55 -0700, JD Conley wrote:
> I was working on some System.Net.Security.SslStream based code and
> noticed the class status page
> (http://mono.ximian.com/class-status/mono-HEAD-vs-fx-2/class-status-Syst
> em.html) shows that the current HEAD implementation does not match the
> naming conventions of the Microsoft .NET libraries.  

The actual code is based on an earlier version of 2.0 (beta 1 IIRC).

> I was going to go
> ahead and implement the "correct" class names and submit a patch, but
> before I do is there any particular reason I shouldn't? :) 

Carlos is (or was, it's been some time since we chatted) working on that
so you should contact him before investing time into it. We sure could
use an hand to ensure this new class gets easier to test than the
current SSL/TLS code.

> I'm building
> code that needs to run under both frameworks and right now I'm deciding
> between updating Mono or writing my own SslStream based on Mono.Security
> and using #if defs (I'd rather do the former).

Mono.Security.dll already contains SslClientStream and SslServerStream
classes (which were based on the MS Fx 1.2 preview API) and was done by
Carlos (and a few bits by me). There are a few known bugs (mostly
related to async support) but they are working, including support for
client, server, SSL3, TLS1, client-side certificates ...

Using them would be easier it you want SSL support on both framework (as
Mono.Security.dll doesn't depend on anything Mono specific) including
1.x versions. Unless you are requiring something special/specific wrt

More information about the Mono-devel-list mailing list