The bad news, as determined by ILSpy, is that there is no way to get to a System.Net.SslStream instance from anywhere inside ASP.NET. That class is used for direct programming against the network, for example by the WCF framework. The best you can do from ASP.NET (whether using System.Web or OWIN on top of IIS … Read more
After communication in comments I can suppose that your main problem is the CN part of the certificate which you use. To have successful TLS communication for IIS Server one have no such strong restrictions like SQL Server has. Microsoft require (see here) that The name of the certificate must be the fully qualified domain … Read more
Until SNI is fully supported, you can only have one certificate per IP address. If you can get a certificate that covers both sites (a wildcard or a UC certificate, for example), you can set up SSL Host Headers to allow both sites to be secured.
It finally worked with the go built in x509.CreateCertificate, the problem was that I did not set the IsCA:true flag, I only set the x509.KeyUsageCertSign which made creating the self signed certificate work, but crashed while verifying the cert chain.
You will have to create an SSLContext to set the Protocoll: in Java 1.8: SSLContext sc = SSLContext.getInstance(“TLSv1.2”); // Init the SSLContext with a TrustManager[] and SecureRandom() sc.init(null, trustCerts, new java.security.SecureRandom()); in Java 1.7: SSLContext sc = SSLContext.getInstance(“TLSv1”); // Init the SSLContext with a TrustManager[] and SecureRandom() sc.init(null, trustCerts, new java.security.SecureRandom()); then you just have … Read more
In VB.Net, you need to write ServicePointManager.ServerCertificateValidationCallback = AddressOf AcceptAllCertifications