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.
>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
[quoted text clipped - 7 lines]
> -Jason Kendall
> JasonKendall@hotmail.com
Jason Kendall - 21 Feb 2005 19:44 GMT
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
>A detailed description of how to add a new code group associated with a
>strong name is available at
[quoted text clipped - 16 lines]
>> -Jason Kendall
>> JasonKendall@hotmail.com
Nicole Calinoiu - 21 Feb 2005 19:55 GMT
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...
> Thank you very much for this Blog reference. It's actually one that I
> ran across during my research.
[quoted text clipped - 35 lines]
>>> -Jason Kendall
>>> JasonKendall@hotmail.com
Jason Kendall - 21 Feb 2005 20:09 GMT
"Sounds like you might be misreading Shawn's article."
Sounds like you're right!
Thanks for hand holding me though finding the solution.
-Jason Kendall
JasonKendall@hotmail.com
>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
[quoted text clipped - 44 lines]
>>>> -Jason Kendall
>>>> JasonKendall@hotmail.com