Trust an assembly (not using.net wizards?)

[Christian W.]

Hello all,

first of all I'm just a simple system administrator and I have no idea how
Framework works - that's why I need your help. Our devoloper team is just in
the process of writing a couple of new programs for internal use. They're
using C# and their programs require the latest Framework version on every
client PC. Using group policies I installed Framework on the clients - no
problem there.

But what I have a problem with - and where I'd need your help - is when it
comes to trusting those applications. Now I have two questions:

1. According to my colleagues you can't write a Framework-based program
without security. So everytime you have a new application or change an
application you have use the "Trust an assembly"-Wizard on every workstation
again. Is that right?

2. If 1.) is right, do you have any idea on how to do that process
automatically ... using i.e. group policies and other means. I don't want to
run around every couple of days (that's about how often our developers
change their programs) to change the trust on about 100 PCs.

I couldn't find any info on that on the web. I'm sure it's out there
somewhere - but as I have no idea on how the whole .NET and framework things
work I hit a wall when it came to understanding the articles. So I gave up
my quest for knowledge on the web and kindly ask you to lend me a hand.

I'd really appreciate any hint you could give me!

Thanks,
Christian.

 

[Mattias Sjögren]

Christian,

1. According to my colleagues you can't write a Framework-based program
without security. So everytime you have a new application or change an
application you have use the "Trust an assembly"-Wizard on every workstation
again. Is that right?

No. You can use the .NET Framework Configuration snap-in to set up a
code group that all your apps will belong to, and specify that they
should get whatever permissions they need. You can for example give
full trust to assemblies with a certain strong name or signed with a
certain publisher certificate.

2. If 1.) is right, do you have any idea on how to do that process
automatically ... using i.e. group policies and other means. I don't want to
run around every couple of days (that's about how often our developers
change their programs) to change the trust on about 100 PCs.

Make the changes on one machine so that they are persisted to
%windir%\Microsoft.NET\Framework\v1.1.4322\CONFIG\enterprisesec.config.
You should then be able to distribute this file to the other machines.



Mattias