Re: Creating MSI for installing .NET security policies
- From: Dominick Baier <dbaier@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 12 Oct 2006 14:11:05 +0000 (UTC)
Hi,
no thats the default behavior. You should write an MSI installer with custom install/uninstall actions to programmatically create the stuff for you.
System.Security.Policy has all the classes you need.
I can dig out some code if you need it.
---
Dominick Baier, DevelopMentor
http://www.leastprivilege.com
Hi folks,
I'm deploying my app to a network share and I need the security
permissions installed on the client. AFAICT I cannot use ClickOnce
because ClickOnce deployment doesnt allow user to specify install
location i.e. Network share. So I have gone down the route of creating
a Strong Name key and signing my assemblies with that key, creating a
new Code Group in the Microsoft .NET configuration Tool which assigns
full trust to my Strong Name key, and then finally creating a
deployment package MSI to allow users to install the Security Policy
easily.
Now, this all works ok, but I find it a bit sas that the security
policies are over written in the Code Groups with the new settings
i.e. they are not merged with the existing groups. Luckily my clients
have a clean slate of policies anyway so I wasnt overwriting anyone
elses, but what if some other vendor had written an app for the client
and had used the same approach, I would scrub there policies, or vice
versa someone could quite easily scrub mine. Is this correct?
Of course policies could be manually added in, but this might be a
pain if there were a lot of users.
Or is there another way I have missed?
Thanks again,
David
.
- Prev by Date: The remote server returned an error: (403) Forbidden in webrequest
- Next by Date: RE: Which encryption type ????
- Previous by thread: The remote server returned an error: (403) Forbidden in webrequest
- Next by thread: Re: Creating MSI for installing .NET security policies
- Index(es):
Relevant Pages
|
