[Mono-bugs] [Bug 55364][Nor] New - We do not report (nor fail) for CS1548 - Cryptographic failure while signing assembly ...

[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=55364

--- shadow/55364	2004-03-09 09:35:38.000000000 -0500
+++ shadow/55364.tmp.413	2004-03-09 09:35:38.000000000 -0500
@@ -0,0 +1,50 @@
+Bug#: 55364
+Product: Mono: Compilers
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: C#
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastien@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: We do not report (nor fail) for CS1548 - Cryptographic failure while signing assembly ...
+
+Description of Problem:
+The most common case for this error is when a strongname key file couldn't
+be found by MCS.
+
+
+Steps to reproduce the problem:
+1. Compile the attached sample with MCS
+
+
+Actual Results (MCS):
+Compilation succeeded
+
+
+Expected Results (CSC):
+CS1548
+
+
+How often does this happen? 
+Always
+
+
+Additional Information:
+The signing job is done in AssemblyBuilder.Save. It seems that this method
+doesn't fail when signing is imposible - so no error is available to MCS.
+
+MCS could do a double-check, that is if AssemblyKeyFileAttribute is present
+then the resulting assembly should be signed or report the CS1548 error.
+
+IIRC the new CSC 1.2 compiler will have a new switch (keyfile) so that the
+AssemblyKeyFile attribute won't be required in the future to sign assembly
+(VBC already go it). This will mean that MCS will requires the signing code
+itself.