after changed the permisssion set to "nothing", I can't set the .net configuration anymore?

after changed the permisssion set to "nothing", I can't set the .net configuration anymore?

Post by tw » Thu, 16 Feb 2006 19:23:36


after I changed the permisssion set of All_Code to "nothing"
, I can't set the .net configuration anymore?

even the Caspol.exe tool can't work anymore.
it just shows that "System.Security.Policy.PolicyException" error?

and the Microsoft .NET Framework 1.1 setting in Control Panel
also can't run....

what can I do to solve this problem, pls?
 
 
 

after changed the permisssion set to "nothing", I can't set the .net configuration anymore?

Post by Nicole Cal » Fri, 17 Feb 2006 05:43:30

One of the consequences of denying local code the right to run is that you
can no longer use the policy modification tools. One can usually work
around the problem relatively simply by editing the policy configuration
files directly. See
http://www.yqcomputer.com/
if you need help locating the configuration file(s) corresponding to the
policy level(s) you have edited.

If there's some specific goal you were trying for when you made this
particular edit and you would like help with it, could you please provide
more details regarding your desired outcome?

 
 
 

after changed the permisssion set to "nothing", I can't set the .net configuration anymore?

Post by Cerebrus9 » Fri, 17 Feb 2006 06:21:37

Hi tw,

IMHO, it may be a better idea to set the CAS Permission level to
"Everything" first, if the program works just fine, then try tightening the
levels. I don't think it would be such a good idea to set the Permission set
to Nothing directly. I'm also interested to see if someone has a better
answer for determining the conflicting security config.

Setting CAS to "Everything" is different from "Full Trust" because no
security checks are performed on the latter.

Regards,

Cerebrus.
 
 
 

after changed the permisssion set to "nothing", I can't set the .net configuration anymore?

Post by tw » Fri, 17 Feb 2006 10:37:26

thank you, Nicole.

I've solve this by modifing the User policy configuration file
"%USERPROFILE%\Application data\Microsoft\CLR security
config\vxx.xx\Security.config".

This error happened because some client cannot execute my .net program.
They had a message as following:
The application attempted to perform an
operation not allowed by the security policy. To grant
this application the required permission please contact
your system administrator or change the application's
trust level in the configuration file.

So I just try to make the same situation to find the answer....