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 for Bug 8563 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I am using a Webservice (i.e. a class derived from SoapHttpClientProtocol) over a https connection using a client certificate for authentication. I set this client certificate by adding it to the ClientCertificates property (defined in HttpWebClientProtocol, the base class of SoapHttpClientProtocol) of my proxy class.
This works just fine, as long as I stick to RSA keys. DSA or ECDSA keys do not work. I analysed some stack traces and browsed the codes, and found out, that the relevant class for actually creating the signature in the handshake is Mono.Security.Protocol.Tls.Handshake.Client.TlsClientCertificateVerify. And there, the code blindly assumes the the AsymmetricAlgorithm object of the private is of type RSA.
I am aware, that there are no usable base methods for signing/decrypting in AsymmetricAlgorithm, which could be easily used, but the logic here could be a bit better. It should at least check for the other implementations of AsymmetricAlgorithm defined by .NET (DSA and ECDsa)