[Mono-devel-list] Re: [Mono-list] CVS users - changes to assemblies signing
spouliot at videotron.ca
Wed Jun 9 16:35:28 EDT 2004
There won't be "official verified assemblies" - at least not for 1.0. Mono
1.0 will ensure package (not assembly) integrity through RPM (and other
packaging signing when possible).
This means that strongnames usage/support in Mono 1.0 is limited to
manageability only (no integrity checks will be done by the runtime).
This may change in a future releases (requiring a new privates keys) once we
build the proper support in Mono and, more important, when we figure out an
easy way for Mono developers and distributors to recompile from source.
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com]On Behalf Of Peter
Sent: 9 juin 2004 16:24
To: spouliot at videotron.ca
Subject: [Mono-devel-list] Re: [Mono-list] CVS users - changes to
Isn't it, um, bad to commit the private key to public CVS? Will there be
a different key for official Ximian-verified system DLL's?
On Wed, 2004-06-09 at 15:46, Sébastien Pouliot wrote:
> We are now starting to fully sign the assemblies. The process selected is
> the one that should be the easiest for developers - most CVS users should
> see the difference to build mono/mcs/... To do so the private keys (for
> Mono and Gtk#) have been commited to CVS. For Mono the "real" signing
> process will be made when you do a "make install" (the sn.exe tool will be
> called just before gacutil.exe). Gtk# assemblies can be signed during
Peter Williams peter at newton.cx
"[Ninjas] are cool; and by cool, I mean totally sweet."
-- REAL Ultimate Power
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list