[Mono-dev] Open source .Net, and TLS 1.1 & 1.2

[Miguel de Icaza]

Hello Edward,

Martin is creating the branch now where we bring the Microsoft SslStream
into Mono as well as his crypto stack.

For details see:

https://trello.com/c/PvUaV89u/16-tls-stack

On Wed, Dec 17, 2014 at 2:21 PM, Edward Ned Harvey (mono) <
edward.harvey.mono at clevertrove.com> wrote:

> I was able to trim this down to a specific subset and make a unit test out
> of it.  Although SslStream has compatibility problems communicating with
> other implementations (such as .Net), mono SslStream also has a problem
> talking to *itself*.  The root causes are the same for both the internal
> compatibility problem, and the external problems.  So the internal problem
> is demonstrated in  the SslStreamTest here:
>
> https://github.com/rahvee/mono/commit/b0362fe70fb445f90197eab712b8d995f88d78e1
>
> Should I submit a pull request?  Note:  This test currently passes on
> .Net, and fails on mono.  I don't know if you guys want me submitting a
> test that is known to fail on mono.
>
> Should I file a bug in bugzilla?  (I'm not sure if I have sufficient
> permission).
>
> And as a matter of style, in the above commit I needed to use some classes
> that weren't available in the MonoTest namespace, so I used
> "global::System....." in several places.  Is this the correct and/or best
> way to deal with it?  Or is there a better way to handle that?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150108/987e96ac/attachment.html>