Security issues

  • Thread starter Thread starter Ken Galer
  • Start date Start date
K

Ken Galer

I am working on a small project that I started at home. It originally was
on the C: drive and was working properly. After bringing it to work I
placed it in a folder on the server with the other projects folders and now
it will not let me run it from VS.

I get a security exception:

/////
An unhandled exception of type 'System.Security.SecurityException' occurred
in JC Test Fixture.exe
Additional information: Security error.
/////

Any ideas?
 
By default, executables on an intranet execute with lower permissions than
executables on your local box. You must change the security policy to raise
the trust level based on that assembly's evidence (trust the location,
signer, etc.) or move the executable.
 
I could not make any sense of that. Where do I change the permissions
level? Whos security policy?

Is this something that is is done is VS or do I have to get the netword
admin involved?

What possible reason would the network think that I don't have rights to a
file that I own and placed in the folder that I made?

What is an "assembly evidence"?

Where can I find information on this problem? Tthe MSDN libray has a load
of information, none that I have found that helps.

Ken
 
Consult
http://msdn.microsoft.com/library/d...NETFrameworkAdministrationToolMscorcfgmsc.asp

and associated pages. You want to "increase assembly trust" with the tool.
This tool does not run under Windows 98SE. I asked a similar question on
this forum as to sharing an assembly resident on an XP system, to execute on
a W98SE system (with the framework installed thereupon), but did not receive
an answer. But if you are sharing across XP systems you should be OK.

Regards,
 
Hi Ken,

Thank you for posting in the community!

Based on my understanding, you created an assembly on your machine, which
works well. Then you move this assembly to another machine, and its access
gets a security exception.

==============================================
I agree with Mickey that your network assembly does not enough permissions.
So you should increase your assembly permission.

The simplest way to get this done is creating a New code group, which use
your assembly's strong name as condition. Then use "FullTrust" permission
set for this code group.

I think you need to know much about .Net Code Access Security theory, there
is a good article talks about this, please refer to "Understanding .NET
Code Access Security" at:
http://www.codeproject.com/dotnet/UB_CAS_NET.asp

This article gives you a step by step sample of how to control access
permission.

==============================================
Please apply my suggestion above and let me know if it helps resolve your
problem.

Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.
Have a nice day!!

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
I was able to get the Framework Configuration snap-in to work but only after
I realized (after about 3 hours) that there were TWO versions to choose from
on my machine. It looks like I was tweaking the one for Version 1.0. When
I used the 1.1 version things started to make sense again. I made a new
Code Group in Runtime Security Policy/Machine/Code Groups and made my mapped
netword drive fully trusted.

Thanks to all


"Jeffrey Tan[MSFT]" said:
Hi Ken,

Thank you for posting in the community!

Based on my understanding, you created an assembly on your machine, which
works well. Then you move this assembly to another machine, and its access
gets a security exception.

==============================================
I agree with Mickey that your network assembly does not enough permissions.
So you should increase your assembly permission.

The simplest way to get this done is creating a New code group, which use
your assembly's strong name as condition. Then use "FullTrust" permission
set for this code group.

I think you need to know much about .Net Code Access Security theory, there
is a good article talks about this, please refer to "Understanding .NET
Code Access Security" at:
http://www.codeproject.com/dotnet/UB_CAS_NET.asp

This article gives you a step by step sample of how to control access
permission.

==============================================
Please apply my suggestion above and let me know if it helps resolve your
problem.

Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.
Have a nice day!!

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Click to expand...
 
Hi Ken,

I am glad you got what you want.
If you have any further concern, please feel free to tell me, I will work
with you.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top