Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80557 --- shadow/80557 2007-01-19 08:31:23.000000000 -0500 +++ shadow/80557.tmp.23224 2007-01-19 08:31:23.000000000 -0500 @@ -0,0 +1,30 @@ +Bug#: 80557 +Product: Mono: Class Libraries +Version: 1.2 +OS: other +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Wishlist +Component: Mono.Security +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: Client Certificate Chains not supported + +I noticed in the ClientCertificate message sent by the SslClientStream and +the ClientCertificate message received by the SslServerStream don't +support Certificate Chains. They only support one Client Certificate. The +Ssl standard supports Client Certificate Chains. + +I made a patch to both the +Mono.Security.Protocol.Tls.Handshake.Client.TlsClientCertificate.cs and +Mono.Security.Protocol.Tls.Handshake.Server.TlsClientCertificate.cs. + +This patches doesn't alter anything in the external interface. Only the +verifyCertificate is changed into verifyCertificates but this shouldn't +matter because it's a private method and it is only called in one place. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
