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=79454 --- shadow/79454 2006-09-20 13:34:44.000000000 -0400 +++ shadow/79454.tmp.3770 2006-09-20 14:02:15.000000000 -0400 @@ -75,6 +75,24 @@ until it can verify the certificate." ------- Additional Comments From [EMAIL PROTECTED] 2006-09-20 13:34 ------- Yes, just noticed that SignedXml.GetPublicKey() does not handle X509Data. Now fixed #1 in svn. Others will follow hopefully. + +------- Additional Comments From [EMAIL PROTECTED] 2006-09-20 14:02 ------- +Great, thanks! + +I think we need to save the list of certificates for the current +KeyInfoX509Data (and reset it if we returned the last one) or store +the enumerator, ottherwise we can't support multiple certificates in +a single X509Data element (or multiple issuer serials, ...). + +I've attached a quick and dirty patch for this which is definitely +not intended to be committed. I'll see if I can get some unit tests +for these scenario's. + +About X509Store: I talked to Sebastien earlier today about +implementing X509Store using CryptoAPI (for Windows only, and use +something else for linux), but he didn't like it. Not sure why, but +I'm sure he has his reasons. However, I don't see another way of +accessing the certificate store on Windows. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
