Re: strong name woes

From: Henning Krause (newsgroup.no_at_spam.infinitec.de)
Date: 05/27/04 

Date: Thu, 27 May 2004 13:42:13 +0200

You can use one key for all assemblies you create.

But you should consider that you must use the signing key the entire
lifecycle of all assemblies that are signed with this key.

So, if someone cracks the signing key or steals it from you, he can create
new assemblies with the same name and the same signature.

Greetings,
Henning Krause
==========================
Visit my website: http://www.infinitec.de
Try my free Exchange Explorer: Mistaya
(http://www.infinitec.de/?page=products)

"ari" <anonymous@discussions.microsoft.com> wrote in message
news:1FDCF6D5-F6F0-4CD4-BD89-50C2F05E3C6E@microsoft.com...
> Can you use 1 key for all your assemblies? Or do you have to create a new
key for each assembly?
> thanks,
> ari

Relevant Pages

  • Re: Appl. Security Problems
    ... > Are there instructions on how trust a directorory and the files within it. ... You would simply need to use a URL membership condition rather than a strong ... unusual to use a different signing key for each project within a solution. ... The "typical" schemes are to use a single signing key for all assemblies ...
    (microsoft.public.dotnet.security)
  • Re: NUnit and StrongnameIdentityPermission
    ... If you are using link demands instead of full stack demands, ... be an issue if you sign your test assembly with the same signing key. ... Re-compile NUnit from its source (available in the NUnit install ... > our company's key on the public interfaces of some of the assemblies. ...
    (microsoft.public.dotnet.security)
  • Re: Sign assembly
    ... The enterprise library ships as source code. ... simply recompile with the signing key of your choice. ... > My assemblies i sign using the visula studio properties dialog but how do ...
    (microsoft.public.dotnet.security)