[Mono-bugs] [Bug 79704][Nor] Changed - [2.0] Cannot load PEM certificate

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Oct 20 09:03:49 EDT 2006


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 sebastien at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=79704

--- shadow/79704	2006-10-20 05:46:15.000000000 -0400
+++ shadow/79704.tmp.4800	2006-10-20 09:03:49.000000000 -0400
@@ -2,22 +2,22 @@
 Product: Mono: Class Libraries
 Version: 1.1
 OS: GNU/Linux [Other]
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
-Component: Mono.Security
+Component: System
 AssignedTo: sebastien at ximian.com                            
 ReportedBy: pawel.sakowski at mindbreeze.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Cannot load PEM certificate
+Summary: [2.0] Cannot load PEM certificate
 
 Description of Problem:
 X509Certificate2 (internally, Mono.Security.X509.X509Certificate) is unable
 to open a PEM-encoded certificate
 
 Steps to reproduce the problem:
@@ -63,6 +63,19 @@
 
 "This constructor creates a new X509Certificate2 object using certificate
 information from a byte array. The byte array can be binary (DER) encoded
 or Base64-encoded X.509 data. The byte array can also be a PKCS7
 (Authenticode) signed file; the signer certificate is used to create the
 object."
+
+------- Additional Comments From sebastien at ximian.com  2006-10-20 09:03 -------
+Yes, there are still many missing features in X509Certificate2 (and
+even more in it's associated classes) but they are 2.0 features. 
+
+The X509Certificate class in Mono.Security main goal was to implement
+corlib's X509Certificate class. The extra features it has were
+required for building our tools (e.g. authenticode support).
+
+Wordaround: Many of Mono tools supports PEM encoded certificates by
+using additional code (as they are built on top of fx 1.1). You could
+easily copy-paste that code into your own (until we complete 2.0
+support into Mono).


More information about the mono-bugs mailing list