Bug 8563 - TLS connections using a client certificate only work with RSA keys
Summary: TLS connections using a client certificate only work with RSA keys
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web.Services ()
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-11-23 05:56 UTC by Mathias
Modified: 2015-03-26 12:06 UTC (History)
2 users (show)

Tags:
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 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 original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Mathias 2012-11-23 05:56:01 UTC
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)