You are right, mine is a real certificate and more I executed the server app on my local server with the correspondent FQDN for which the certificate itself is released.
Really nice the article from Miguel's blog, thanks for pointing me to that. I'm afraid that your mono fork not available but as you said may you found your working copy of that and hopefully you can build up a serial patch which I interested to look for. I also tried to run the mentioned server/client example using DNXCore5.0 ( http://blogs.msdn.com/b/dotnet/archive/2014/12/04/introducing-net-core.aspx ) using follow references "System.Net.Sockets": "4.1.0-beta-23217", "System.Net.Primitives": "4.0.11-beta-23301", "System.Net.Security": "4.0.0-beta-23220", "System.Security.Cryptography.X509Certificates": "4.0.0-beta-23301", but the results was exactly the same, in fact the net core relies on the host framework that in Linux is mono, but at this point I think I'll look for the next TLS implementation steps directly from the mono git updates. Actually I'm figuring which IDE I can use to browse using intellisense the source code of the mono ( may mono-develop? and if yes, which is the solution file ? :) -- View this message in context: http://mono.1490590.n4.nabble.com/SslStream-X509-certificate-tp4666570p4666574.html Sent from the Mono - Dev mailing list archive at Nabble.com. _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
