[Mono-bugs] [Bug 68903][Nor] New - ASN.1 doesn't support undefined length encoding

[bugzilla-daemon@bugzilla.ximian.com]

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@ximian.com.

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

--- shadow/68903	2004-10-28 15:11:33.000000000 -0400
+++ shadow/68903.tmp.12261	2004-10-28 15:11:33.000000000 -0400
@@ -0,0 +1,37 @@
+Bug#: 68903
+Product: Mono: Class Libraries
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Mono.Security
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastien@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: ASN.1 doesn't support undefined length encoding
+
+Description of Problem:
+
+The current ASN.1 class doesn't decode properly objects encoding with
+undefined length encoding (length == 0x80). This was a known issue and is
+not a problem for most structures (like X.509 certificates used in Mono). 
+
+However I just found out that the SPC files provided by VeriSign are
+(a) not binary - they are Unicode
+(b) contains the ASN.1 data in base64
+(c) Use undefined length encoding :(
+
+(a) and (b) aren't much a problem.
+
+
+Current workaround (for Windows users)
+1. Import the SPC file (double-click) in the certificate manager;
+2. Export the new certificate(s) in .DER format;
+3. Execute CER2SPC (Mono or MS version) to construct a SPC file encoded
+"properly" ;-)