[Mono-devel-list] Re: Signing problems

Sebastien Pouliot sebastien at ximian.com
Wed Jul 28 22:07:57 EDT 2004


I know two problems that can results in this error.

First, an old (pre mono beta, like 0.31) Mono.Security.dll is being used
- but I doubt this is the case.

Second, the token mapping resides in machine.config. Without the mapping
(ECMA token to Mono public key) mscorlib can't be signed.

So the side-by-side installation probably results in having different
machine.config (one for each supported runtime), so my best guess is
that one of the (or the two ;-) machine.config files don't have the
mapping information (like the one that resides in CVS).

On Wed, 2004-07-28 at 18:32, Duncan Mak wrote:
> Hey Raja,
> I think because of Lluis' new side-by-side installation changes, we are
> now seeing problems on build-a-tron regarding signing. The error is:
> make[7]: Entering directory `/home/builder/HEAD/mcs/class/corlib'
> MONO_PATH="../../class/lib/default:$MONO_PATH" mono  ../../tools/security/sn.exe -q -R ../../class/lib/default/mscorlib.dll ../../class/mono.snk
> Couldn't sign the assembly ../../class/lib/default/mscorlib.dll with this key pair.
> make[7]: *** [../../build/deps/default_corlib.dll.was_signed] Error 1
> make[7]: Leaving directory `/home/builder/HEAD/mcs/class/corlib'
> make[6]: *** [all.real] Error 2
> make[6]: Leaving directory `/home/builder/HEAD/mcs/class/corlib'
> If you could take a look at this, that'd be great.
> Duncan.
Sebastien Pouliot <sebastien at ximian.com>

More information about the Mono-devel-list mailing list