[Mono-dev] TLS Providers
Miguel de Icaza
miguel at microsoft.com
Mon Oct 17 19:10:48 UTC 2016
What we want to do is to allow the user to configure at build time whether to use BoringSSL that we maintain, or use a system installed version of OpenSSL, that way Mono does not have to ship with the crypto, and if you update your OpenSSL installation on the system, the updates will flow into Mono directly.
From: Mono-devel-list <mono-devel-list-bounces at lists.dot.net> on behalf of "Zinkevicius, Matt" <matt.zinkevicius at hpe.com>
Date: Friday, September 30, 2016 at 11:09 PM
To: "mono-devel-list at lists.dot.net" <mono-devel-list at lists.dot.net>
Subject: [Mono-dev] TLS Providers
Congrats to the team on the new BoringSSL TLS backend!
Our team is attempting to get our appliance FIPS certified to be able to sell into the US government. In our case, we must use the pre-approved version of OpenSSL that’s installed on the box. My question is whether the plan is still to allow developers to provider their own TLS provider assemblies (as described in http://www.mono-project.com/docs/about-mono/releases/4.6.0/#potentially---tls<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.mono-project.com%2Fdocs%2Fabout-mono%2Freleases%2F4.6.0%2F%23potentially---tls&data=01%7C01%7Cmiguel%40microsoft.com%7C4afd3edad29b4af4125408d3e9a852f8%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=NC4GxM8s%2F%2FD4TcSnq%2BcY%2Fa7pZDl0Ca993ovnImir9og%3D&reserved=0>)? I ask since reading the code in master seems to suggest this may no longer be the case.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list