[Mono-devel-list] Assembly referencing on Windows - Mono Tricks?
spouliot at videotron.ca
Mon Sep 20 13:56:37 EDT 2004
Indeed Mono use the same public key. This is required to get the same public
key token. And no we don't, and never will, have access to MS private keys.
This problem was (kind of) solved by ECMA when they introduced the ECMA key.
We only generalized the same "remapping" concept to include other public
keys using by Microsoft (and a few others).
You can have a look at my blog if you are interested in more details. There
are also some documents in the monkeyguide that talks about this (but they
may only be in CVS). Finally the source code of sn.exe, in
/mcs/tools/security/, should answer anything not properly documented ;-).
home: spouliot at videotron.ca
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com]On Behalf Of Aaron
Sent: 20 septembre 2004 11:28
To: mono-devel-list at lists.ximian.com
Subject: [Mono-devel-list] Assembly referencing on Windows - Mono
I have been trying to figure out which assemblies are
getting used when I compile with csc and msc and then
execute with mono or the MS clr, all on Windows.
I thought a good way would be to look at the strong
name of the loaded assemblies but it appears mono is
mirroring the .Net GAC, if not in exact contents at
least in assembly names, and is using not only the
same names and versions but also the same public key?
This would make sense in order to allow apps compiled
against .Net to run against mono without recompiling.
However, doesn't this raise a security concern since
the mono assemblies can't be signed with the private
key (since it belongs to MS) and are therefore loading
strong named assemblies that are falsely signed? Or am
I just way off track?
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list