On Jun 27, 2012, at 5:53 PM, Igor Russkih wrote:
> Moreover, Mono.Security assembly is shipped stripped, in particular it misses 
> StrongName class - so even manual validation is not possible.

Odd; my Mono.Security.dll contains it.

> What is the background behind these decisions?

I don't know why strong named assemblies aren't validated for you; we'd need a 
test case for this.

I do know that we screwed up when we started signing Mono.Android.dll and the 
other BCL assemblies, as they're not signed with a proper key; they're delay 
signed, and then never signed (because they're using the .NET public key, so we 
can't actually sign them at all; Doh!).

 - Jon

_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Reply via email to