From: Miguel de Icaza [mailto:mig...@xamarin.com]
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
Thanks
___
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.m...@clevertrove.com wrote:
I was
From: Miguel de Icaza [mailto:mig...@xamarin.com]
We have implemented TLS 1.1 and 1.2 on top of the not yet open sourced
networking stack and will be publishing it as soon as Microsoft open sources
the .NET networking stack.
Have there been unpublished changes to
bump
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Edward Ned Harvey (mono)
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
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
On Dec 15, 2014, at 6:54 AM, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
I'll look into __MonoCS__ to see if it does what I'm looking for.
It is not what you're looking for. __MonoCS__ is defined by the Mono C#
compiler (mcs); that's all it means.
It doesn't mean that
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Edward Ned Harvey (mono)
From: Miguel de Icaza [mailto:mig...@xamarin.com]
We would love a test case to add to the test suite.
We are building a new test suite as part of
From: Alexander Köplinger [mailto:alex.koeplin...@outlook.com]
I'm curious: why do you need it to compile with MS.NET if you're testing
Mono stuff?
This particular test fails on current mono. So it's not sufficient to just see
it fail on mono - to have any value it has to demonstrate
source .Net, and TLS 1.1 1.2
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Eberhard Beilharz
Wouldn't
#if __MonoCS__
do what you want?
Yeah, that works. Thanks! It's funny though, as I search around for
__MonoCS__
From: Alexander Köplinger [mailto:alex.koeplin...@outlook.com]
We can add it to the website, do you have a suggestion on which page it
makes the most sense? On the FAQ pages perhaps?
I don't have any suggestion better than FAQ. It's unlikely that a person like
me will find it all by
Do we not have a flag for if it's compiled for tests, rather than release?
On 14 Dec 2014 05:14, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: Miguel de Icaza [mailto:mig...@xamarin.com]
We would love a test case to add to the test suite.
We are building a
From: mar...@my2cents.co.uk [mailto:mar...@my2cents.co.uk] On Behalf
Of Martin Thwaites
Do we not have a flag for if it's compiled for tests, rather than release?
I don't need a flag to distinguish between tests release - I need one to
determine if the test is being run on mono or windows.
From: Alexander Köplinger [mailto:alex.koeplin...@outlook.com]
You can find out if you run on Mono by checking if Type.GetType
(Mono.Runtime) != null.
That's helpful, but doesn't quite solve it, because compilation will fail on
windows ...
I'm looking for something like this...
#ifdef
Using Reflection maybe?
On Sun, Dec 14, 2014, 15:45 Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: Alexander Köplinger [mailto:alex.koeplin...@outlook.com]
You can find out if you run on Mono by checking if Type.GetType
(Mono.Runtime) != null.
That's helpful,
I'm curious: why do you need it to compile with MS.NET if you're testing Mono
stuff?
-- Alex
From: edward.harvey.m...@clevertrove.com
To: alex.koeplin...@outlook.com
CC: mono-devel-list@lists.ximian.com
Subject: RE: [Mono-dev] Open source .Net, and TLS 1.1 1.2
Date: Sun, 14 Dec 2014 17:44
Wouldn't
#if __MonoCS__
do what you want?
Mono edward.harvey.m...@clevertrove.com wrote on 2014-12-14 at 18:44 +0100:
From: Alexander Köplinger [mailto:alex.koeplin...@outlook.com]
You can find out if you run on Mono by checking if Type.GetType
(Mono.Runtime) != null.
That's helpful, but
From: Miguel de Icaza [mailto:mig...@xamarin.com]
We would love a test case to add to the test suite.
We are building a new test suite as part of this work anyways.
This is almost done. Granted it is microscopic in scope - the test I've
written tests only for the case that I know fails;
Does anybody know if support for TLS 1.1 1.2 will be released, and if so,
going to be integrated into mono?
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hello,
.NET's implementation of the TLS stack is built on top of native code, so
it wont work on Mono.
We have implemented TLS 1.1 and 1.2 on top of the not yet open sourced
networking stack and will be publishing it as soon as Microsoft open
sources the .NET networking stack.
Miguel
On Tue,
From: Miguel de Icaza [mailto:mig...@xamarin.com]
.NET's implementation of the TLS stack is built on top of native code, so it
wont work on Mono.
We have implemented TLS 1.1 and 1.2 on top of the not yet open sourced
networking stack and will be publishing it as soon as Microsoft open
Hello,
We would love a test case to add to the test suite.
We are building a new test suite as part of this work anyways.
MIguel
On Tue, Dec 9, 2014 at 3:21 PM, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: Miguel de Icaza [mailto:mig...@xamarin.com]
.NET's
I believe there already is one. If you look back to the (awful) mono
pull requests thread I believe it was mention specifically as an
example.
On Tue, Dec 9, 2014 at 11:09 PM, Miguel de Icaza mig...@xamarin.com wrote:
Hello,
We would love a test case to add to the test suite.
We are building
22 matches
Mail list logo
