Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 18766 [details]
Sample project demonstrating the Mono TLS 1.2 client failure when loading an image from a HTTPS address
Mono now has TLS 1.2 support: http://tirania.org/blog/archive/2016/Sep-30.html
According to this post on stackoverflow the Mono TLS 1.2 client should work on Xamarin:
Yet in my Xamarin.Forms (Android version) I cannot connect to HTTPS web sites to download an image:
This is the error I get:
Image Loading: Error getting stream for https://randomuser.me/api/portraits/men/85.jpg?random=0b8505c128554c9f982cfa4fdc169f5e: System.Net.WebException: Error: SecureChannelFailure (The authentication or decryption has failed.) ---> System.IO.IOException: The authentication or decryption has failed. ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: The authentication or decryption has failed.
at Mono.Security.Protocol.Tls.RecordProtocol.EndReceiveRecord (System.IAsyncResult asyncResult) [0x0003a] in /Users/builder/data/lanes/3511/77cb8568/source/mono/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/RecordProtocol.cs:430
at Mono.Security.Protocol.Tls.SslClientStream.SafeEndReceiveRecord (System.IAsyncResult ar, System.Boolean ignoreEmpty) [0x00000] in /Users/builder/data/lanes/3511/77cb8568/source/mono/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslClientStream.cs:256
at Mono.Security.Protocol.Tls.SslClientStream.NegotiateAsyncWorker (System.IAsyncResult result) [0x00071] in /Users/builder/data/lanes/3511/77cb8568/source/mono/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslClientStream.cs:418
--- End of inner exception stack trace ---
I've attached a small sample project that reproduces the issue.
Here is a relevant forum response to try with regards to this bug:
Although you should be able to work around it, we will still want to investigate the TLS support for these Ciphers.
This is resolved as of the current Alpha channel with TLS fixes to Mono's implementation. Thus I would confirm this as "Resolved Upstream".
Fixes in the sense that a new SSL/TLS implementation is used by default over Mono's implementation. On Android it's BoringSSL and on iOS it's AppleTLS.