Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Security / May 2005

Tip: Looking for answers? Try searching our database.

How many keys?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ryan Taylor - 23 May 2005 19:58 GMT
Hello.

I am developing an application with multiple assemblies. I have all the
projects contained in one solution just to make code management a little
easier. However, is it recommended to have one key for strong naming for all
the assemblies (projects) or should if assembly be strong named with a
different key?

Thanks.
Ryan
Alek - 24 May 2005 02:35 GMT
Ryan,

You can use one key. There is no advantages of using multiple keys.

Alek

> Hello.
>
[quoted text clipped - 6 lines]
> Thanks.
> Ryan
Joe Kaplan \(MVP - ADSI\) - 24 May 2005 02:54 GMT
The only reason I can think of that you might want different strong names
would be to apply different security policies to different assemblies and
wanted to use the strong name as evidence.  Otherwise, I agree with Alex.
You probably just want one key.

Joe K.

> Ryan,
>
[quoted text clipped - 12 lines]
>> Thanks.
>> Ryan
Nicole Calinoiu - 24 May 2005 11:57 GMT
Even though it's quite common to use only the public key when using strong
name evidence, other parts of the strong name can also be used when
constructing strong name membership conditions or identity permission
demands.  Since it's possible to vary permission grants based on strong name
without varying the signing key, potential policy use probably shouldn't be
a factor when selecting a signing key.

"Joe Kaplan (MVP - ADSI)" <joseph.e.kaplan@removethis.accenture.com> wrote
> The only reason I can think of that you might want different strong names
> would be to apply different security policies to different assemblies and
[quoted text clipped - 19 lines]
>>> Thanks.
>>> Ryan
Ryan Taylor - 24 May 2005 13:14 GMT
Thanks guys. Seems to be unanimous.

Ryan

> Even though it's quite common to use only the public key when using strong
> name evidence, other parts of the strong name can also be used when
[quoted text clipped - 27 lines]
>>>> Thanks.
>>>> Ryan

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.