Security Policy Confusion...

From: DT (dt_at_nospam.co.uk)
Date: 10/26/04 

Date: Tue, 26 Oct 2004 22:26:42 +0100

Hi,

    In an effort to learn about the .NET security settings I tried a simple
experiment. I created a noddy console application and assigned it a strong
name. I then extracted the public key token from the assembly. This was
all on my local disk. I then tried stop the console application be executed
be giving it the permission set of 'Nothing' using the .NET configuration
tool.

Here are the steps I took

1) I created a new code group in the user code groups section under all
code.
2) I then set the condition type to 'Strong Name' and supplied the token
from my assembly.
3) I then set the permission set to 'Nothing'

Once I'd completed this I tried to run the console application again, and it
runs fine? I expected it to be denied execution rights?

Can anybody help me in making sense of my mistakes / misunderstanding?

Any url's to articles would be a great help!

many thanks

DT

Relevant Pages

  • Code access security policy doubts.
    ... >were I need to set the code group policy. ... Right-click the Everything permission set and select ... Rename the permission set No FileDialog. ... >Exception thrown by the CLR. ...
    (microsoft.public.dotnet.security)
  • Code access security policy doubts.
    ... were I need to set the code group policy. ... Expand the Runtime Security Policy node, ... Right-click the Everything permission set and select ... Select the No FileDialog permission set and click Next. ...
    (microsoft.public.dotnet.security)
  • Re: CAS Policy issue
    ... Any given code group can be marked as exclusive ... the managed user control always runs. ... The default permission set for this code group is ... If you're trying to troubleshoot CAS permission problems, ...
    (microsoft.public.dotnet.security)
  • Re: CAS Policy issue
    ... the managed user control always runs. ... The default permission set for this code group is Nothing. ... If you're trying to troubleshoot CAS permission problems, I'd recommend resetting your CAS policy. ... One easy way to test this would be to assign the FullTrust permission set to your URL-based code group. ...
    (microsoft.public.dotnet.security)
  • RE: Article : Code Access Security Part - 2 (.Net FrameWork Tools Seri
    ... > Before we start with our sample app we need to view the security ... > local mahinc policy MyComputer Zone has Full trust permission set. ... > that we will need to change the Intranet Permission set. ... > To create a code group under intranet with fulltrust to a particular share ...
    (microsoft.public.dotnet.framework.windowsforms.designtime)