Bug 45069 - SslStream AuthenticateAsClient hangs
Summary: SslStream AuthenticateAsClient hangs
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 6.0.0
Hardware: Other Linux
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2016-10-05 16:14 UTC by 1iveowl
Modified: 2017-07-06 19:36 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description 1iveowl 2016-10-05 16:14:29 UTC
This code hangs:

var secureStream = new SslStream(_writeStream, true, CertificateErrorHandler);
secureStream.AuthenticateAsClient(address, null, SslProtocols.Tls, false);

No exception, nothing. AuthenticateAsClient never returns. CertificateErrorHandler called either.

The same code Works fine with .NET on Windows.

I've tested this on Android 6.0 (Marshmellow) API 23. 

Could this be related to this?: https://forums.xamarin.com/discussion/51622/sslstream-authenticateasclient-hangs
Comment 1 Cody Beyer (MSFT) 2017-07-06 19:36:47 UTC
Unfortunately, we’re unable to reproduce this report. If this issue is still occurring for you, please reopen this issue and attach a reproduction to the bug by starting with a clean Xamarin.Android project adding just the code necessary to demonstrate the issue.