By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,640 Members | 1,598 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,640 IT Pros & Developers. It's quick & easy.

Question about modify security policy in client machine

P: n/a
Hi everybody,

I'm facing a problem to run an appliation in a shared network drive. The
application is developed in VB2005. I understand I have to add a signature
with strong name key to all assambies. I found that I have to modify
security policy to trust strong names.

I want to clarify the followings:
1. Does it mean I have to modify the security policy for each client machine
which runs my application in network drive?
2. Is there an easier way to modify the security policy for client machine
if the answer of question 1 is yes? For example, is it possible to do this
in installation procedure using .msi file?
3. For the client machine (one is Vista Business) which does not install
..NET Framework SDK, I can't find .NET Framework Configuration Utility
(mscorcfg.msc). So I don't know how I can modify the security policy.

The article in http://blogs.msdn.com/shawnfa/archiv.../20/57023.aspx
is my major information source.

Thanks for your attention and kindly help!

Regards,
James
Sep 10 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
James Wong wrote:
I want to clarify the followings:
1. Does it mean I have to modify the security policy for each client machine
which runs my application in network drive?
Yes.
2. Is there an easier way to modify the security policy for client machine
if the answer of question 1 is yes? For example, is it possible to do this
in installation procedure using .msi file?
Probably, but I've never had to (I'm lucky that way).
3. For the client machine (one is Vista Business) which does not install
.NET Framework SDK, I can't find .NET Framework Configuration Utility
(mscorcfg.msc). So I don't know how I can modify the security policy.
Use caspol.exe instead - OK, it's a command-line thing but at least it
ships with the Framework, not the SDK.

HTH,
Phill W.
Sep 10 '08 #2

P: n/a
I have run into this problem also. What I did was to create a test
certificate (click on the "Create Test Certificate" button in the
Signing tab of Project/Properties). Then I deploy my app on the network
using "Click Once".

This seems to be good for about a year then it asks again for a new
Signing authority so I recreate the test certificate. Well, this is
what worked for me.

Rich

*** Sent via Developersdex http://www.developersdex.com ***
Sep 10 '08 #3

P: n/a
Hi Phil,

Thanks for your reply! The information about caspol is useful to solve my
problem. I think I have to find an easy way to execute caspol in client
machine (esp. the end users don't have admin. right and know nothing about
Framework).

Regards,
James

"Phill W." wrote:
James Wong wrote:
I want to clarify the followings:
1. Does it mean I have to modify the security policy for each client machine
which runs my application in network drive?

Yes.
2. Is there an easier way to modify the security policy for client machine
if the answer of question 1 is yes? For example, is it possible to do this
in installation procedure using .msi file?

Probably, but I've never had to (I'm lucky that way).
3. For the client machine (one is Vista Business) which does not install
.NET Framework SDK, I can't find .NET Framework Configuration Utility
(mscorcfg.msc). So I don't know how I can modify the security policy.

Use caspol.exe instead - OK, it's a command-line thing but at least it
ships with the Framework, not the SDK.

HTH,
Phill W.
Sep 11 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.