[Mono-bugs] [Bug 55364][Min] Changed - We do not report (nor fail) for CS1548 - Cryptographic failure while signing assembly ...
Tue, 23 Mar 2004 21:50:35 -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 email@example.com.
--- shadow/55364 2004-03-23 20:54:29.000000000 -0500
+++ shadow/55364.tmp.20618 2004-03-23 21:50:35.000000000 -0500
@@ -74,6 +74,19 @@
It is possible, by using AssemblyBuilder, to create assemblies
contaning AssemblyKeyFileAttribute even when the specified file
CSC reports the CS1548 error in this case.
MCS currently generates the assembly (as it rely only on AssemblyBuilder).
+------- Additional Comments From firstname.lastname@example.org 2004-03-23 21:50 -------
+After further tests it appears that attributes do not control the
+signing process (as currently implemented). It is possible to have
+attributes without signatures and signatures without attributes.
+This means we cannot strongname assemblies without modifying mcs (like
+the current approach) but this should solve
+(a) reporting CS1548 when key file is not found;
+(b) the new /keyfile, /keycontainer, /delaysign parameters in 1.2;
+without requiring mcs to link with Mono.Security.dll.
+Suddenly it all make sense ;-)