> On Jun 12, 2017, at 3:19 PM, trollanderson <f60...@mvrht.net> wrote:
>
> Hi,
>
> I'm trying to use Mono to consume a webservice, however I'm getting error
> messages like "No such TLS Provider" and "TLS Support not available" ...
> I have already tested with version 4.8 and 5.0 of mono, but I can not enable
> TLS1.2 usage in CentOS 6.8 / 6.9
>
> I also did the following test: MONO_TLS_PROVIDER = btls csharp -e 'new
> System.Net.WebClient () .DownloadString ("https://www.howsmyssl.com/";)' |
> Grep "TLS 1.2"
>
> Same mistake…In order to make this work on CentOS, I instead opted to use a squid proxy with ssl-bump to terminate SSL on the server, and to negotiate a TLS 1.2 connection to the external server. It’s a crappy solution, but it will work regardless of Mono’s support for TLS 1.2, and when SSL is fixed and deployable, it’s easy to remove. Using it on a localhost introduces little if any latency. > > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/Use-TLS1-2-on-CentOS-Mono4-8-tp4670899.html > Sent from the Mono - Dev mailing list archive at Nabble.com. > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.dot.net > http://lists.dot.net/mailman/listinfo/mono-devel-list
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.dot.net http://lists.dot.net/mailman/listinfo/mono-devel-list
