[Mono-dev] Status of SslStream and Related Classes

JD Conley jd.conley at coversant.net
Fri Aug 12 03:52:04 EDT 2005

> > I'm building
> > code that needs to run under both frameworks and right now I'm
> > between updating Mono or writing my own SslStream based on
> > 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
> 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
> Mono.Security.dll doesn't depend on anything Mono specific) including
> 1.x versions. Unless you are requiring something special/specific wrt
> SSL ?

I will have a look at Mono.Security.  Right now the code base is
compiling (and mostly working) on both the MS.Net 2.0 Beta 2 and Mono
1.1.8 2.0 libraries.  Tls is one of the few remaining sticking points.
I don't need anything special.

After I sent the original email I went ahead and ifdef'd for Mono's Beta
1 style representation of the SslStream and related naming.  I got some
NotImplementedException's on the SslStream.ClientAuthenticate that says
100% implemented with no TODO in HEAD (haven't looked into it yet).
Hopefully it's been added since 1.1.8 release I'm running with.


More information about the Mono-devel-list mailing list