Re: Assign Trust Level to all Assemblies signed with the same Public Key?

From: Nicole Calinoiu (calinoiu)
Date: 02/21/05 

Date: Mon, 21 Feb 2005 14:55:49 -0500

Sounds like you might be misreading Shawn's article. If you omit the steps
in the last section ("To modify the policy to allow full trust for all
Intranet assemblies"), you should end up with a policy modification that
causes all assemblies signed with your public key to be fully trusted when
run from the intranet without enabling full trust of assemblies not signed
with your key. If you can't get to this point, it might help if you could
post back with a slightly more specific question regarding the area(s) with
which you are having trouble...

"Jason Kendall" <JasonKendall@hotmail.com> wrote in message
news:scek1157ag8r1s20b0fb8ggk3o05ssgupd@4ax.com...
> Thank you very much for this Blog reference. It's actually one that I
> ran across during my research.
>
> The problem is that this Blog shows how to do two extremes but not the
> item in the middle that I'm looking for.
>
> I know how to trust an assembly by strong name, and this is how I'm
> doing it today...
>
> I know how to trust everything on the Intranet.
>
> What I'd like to do is trust everything signed with a particular key
> so that I don't have to trust each strong named assembly individually,
> but I also don't fully trust everything on the Intranet.
>
>
> -Jason Kendall
> JasonKendall@hotmail.com
>
>
>
>
>
> On Mon, 21 Feb 2005 14:31:45 -0500, "Nicole Calinoiu" <calinoiu
> REMOVETHIS AT gmail DOT com> wrote:
>
>>A detailed description of how to add a new code group associated with a
>>strong name is available at
>>http://blogs.msdn.com/shawnfa/archive/2003/06/20/57023.aspx. You may need
>>to modify the steps to add the newly created group under a different
>>existing group if you want to affect code run from a location other than
>>the
>>intranet. For example, if you want to modify permissions granted to code
>>run from the local machine, you would add the new group under the
>>My_Computer_Zone group rather than under the LocalIntranet_Zone group.
>>
>>
>>
>>"Jason Kendall" <JasonKendall@hotmail.com> wrote in message
>>news:861k11ttr186s2prhh1bpe2aggjl0or40s@4ax.com...
>>>I work in a law firm and all of the applications built by my team are
>>> used solely internally. I have read help on CAS and caspol.exe, but I
>>> am unable to answer my own question.
>>>
>>> Can I assign a trust level to all assemblies signed with a given
>>> public (private) key?
>>>
>>> Thanks.
>>>
>>> -Jason Kendall
>>> JasonKendall@hotmail.com
>>>
>>
>

Relevant Pages

  • Re: How to test if my code have "FullTrust" permission?
    ... intranet does not necessarily mean that it is not susceptible to use by ... you didn't mention the clients in your "full control of the whole ... >> Unless your code must call into assemblies that do not permit partially ... running with full trust ...
    (microsoft.public.dotnet.security)
  • signed assembly
    ... increase the trust level for the intranet sites to Full ... I can't just trust assemblies with a particular ... I'm embedding my user controls in web pages via ...
    (microsoft.public.dotnet.security)
  • Re: Assign Trust Level to all Assemblies signed with the same Public Key?
    ... >causes all assemblies signed with your public key to be fully trusted when ... >run from the intranet without enabling full trust of assemblies not signed ... >> Thank you very much for this Blog reference. ...
    (microsoft.public.dotnet.security)
  • Re: Assign Trust Level to all Assemblies signed with the same Public Key?
    ... Thank you very much for this Blog reference. ... I know how to trust an assembly by strong name, ... I know how to trust everything on the Intranet. ... >> Can I assign a trust level to all assemblies signed with a given ...
    (microsoft.public.dotnet.security)
  • Re: Running a local exe as Partially trusted.
    ... Alternatively, if you don't want to modify the code, you could modify the ... security policy and create a code group giving certain trust to your ...
    (microsoft.public.dotnet.security)