[Mono-bugs] [Bug 55364][Nor] New - We do not report (nor fail) for CS1548 - Cryptographic failure while signing assembly ...
Tue, 9 Mar 2004 09:35:38 -0500 (EST)
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 firstname.lastname@example.org.
--- 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 @@
+Product: Mono: Compilers
+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):
+Expected Results (CSC):
+How often does this happen?
+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