[Mono-devel-list] [PATCH] Strongname signature verification
spouliot at videotron.ca
Fri May 14 11:11:26 EDT 2004
Possibly. Right now if you want to use Mono.* assemblies on the MS runtime
you must turn off signature verification on them.
You can do this by executing (ms version) of sn.exe
sn -Vr Mono.Data.SqliteClient,0738eb9f132ed756
where 0738eb9f132ed756 is the public key token (which can be found using
sn -Tp Mono.Data.SqliteClient.dll).
You can replace Mono.Data.SqliteClient by * to skip verification for all
assemblies containing the Mono public key.
From: Chris Turchin [mailto:chris at cigale.pelemele.com]On Behalf Of Chris
Sent: 14 mai 2004 11:01
To: Sébastien Pouliot
Subject: Re: [Mono-devel-list] [PATCH] Strongname signature verification
is this why I could not reference Mono.Data.SqliteClient.dll in a VB.NET
On Fri, 14 May 2004, Sébastien Pouliot wrote:
> Hello all,
> Currently most assemblies in Mono are only delay-signed (i.e. they aren't
> signed but contain the public key). While this is "enough" to get a fully
> qualified name (for GACing) this isn't the "real thing".
> The attached path add signature verification for assemblies outside the
> Assemblies inside the GAC aren't verified at runtime (performance gain)
> they are (or in this case will be verified) at installation time by
> gacutil.exe. Note that this is exactly what the MS runtime already do on
> Comments welcome ;-)
> Sebastien Pouliot
More information about the Mono-devel-list