[Mono-bugs] [Bug 70318][Nor] Changed - Strong name validation failed for module Mono.security.dll

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 14 Dec 2004 09:40:01 -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 sebastien@ximian.com.


--- shadow/70318	2004-12-08 05:43:27.000000000 -0500
+++ shadow/70318.tmp.25433	2004-12-14 09:40:00.000000000 -0500
@@ -1,16 +1,16 @@
 Bug#: 70318
-Product: Mono: Class Libraries
+Product: Mono: Runtime
 Version: 1.0
+OS: Windows XP
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Normal
-Component: Mono.Security
+Component: packaging
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: banil@novell.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 Summary: Strong name validation failed for module Mono.security.dll
@@ -34,6 +34,28 @@
 How often does this happen? 
 Additional Information:
+------- Additional Comments From sebastien@ximian.com  2004-12-14 09:39 -------
+The packaged version of Mono.Security.dll assembly (and maybe others)
+has not been fully signed in the Mono 1.0.4 package for Windows.
+Mono can use this delay-signed assembly but the MS runtime won't (by
+A workaround is to sign the assembly yourself by:
+1. Downloading the strongname key pair
+wget http://svn.myrealbox.com/source/trunk/mcs/class/mono.snk
+2. Strongname the assembly
+sn -R Mono.Security.dll mono.snk
+Note: You can use Mono's or MS version of SN to do this last step.
+Once signed the assembly can be installed in the GAC (if required) by
+gacutil and used by the MS runtime.