Re: Custom Principal Permission (non-CodeAccessPermission derived) not working

From: Marcelo Birnbach [MS] (mbirnbac_at_online.microsoft.com)
Date: 06/28/03

  • Next message: Marcelo Birnbach [MS]: "Re: Code Group Security policy deployment" 
    Date: Fri, 27 Jun 2003 15:28:52 -0700

    What do you mean with declarative permission is ignored? If you don't add
    your permission to the security policy, it's likely that your assembly won't
    have this permission and fail on a Demand. Can you explain what are you
    trying to do using declarative security and how do you grant your permission
    without modifying the security policy?

    Thanks,
    Marcelo

    "Olivier Haddad" <olivier.hadad@emblaze.com> wrote in message
    news:OOFFO8wODHA.3700@tk2msftngp13.phx.gbl...
    > I wrote a simple class implementing IPermission and a corresponding
    > attribute class deriving from SecurityAttribute.
    >
    > My permission class does not derive from CodeAccessPermission as I am not
    > interested in a stack walk (like PrincipalPermission).
    >
    > I didn't add the assembly to the Security Policy as MSDN states that it is
    > not needed for non-CAS permissions.
    >
    > Imperative permission works fine, but declarative permission is ignored.
    > Checking the compiled file with ILDasm and Permview revealed that no XML
    > permission metadata was added.
    >
    > How do I get my Security Attribute derivated class to work?
    >
    > The MSDN documentation only gives proper examples for CodeAccessSecurity
    > derived classes.
    >
    >
    >

  • Next message: Marcelo Birnbach [MS]: "Re: Code Group Security policy deployment"

    Relevant Pages

    • Re: [TOMOYO 15/15] LSM expansion for TOMOYO Linux.
      ... This approach doesn't mess up user-supplied buffer. ... a file descriptor said "read ready" but readgets an error ... if security policy or security-id of the file has changed ... I think checking permission at dequeue time ) ...
      (Linux-Kernel)
    • Re: please help with file access and security issues
      ... If that is not the case try resetting the security policy ... > this application the required permission please contact your system ... So I sent him a little app to try and ... > Naturally the message box showed the second message about trying ...
      (microsoft.public.dotnet.security)
    • Re: How do I share .net applications from a network location
      ... > allowed by the security policy. ... > permission please contact your system administrator, ... > the Microsoft .NET security policy administration tool." ... > need to update the trust level every time on all client ...
      (microsoft.public.dotnet.general)
    • Re: Adding permissions to predefined permission sets
      ... The information concerning an inability to modify the predefined permission ... could modify security policy directly by changing those files and was ... > need to copy the permission set, modify it, then change the permission set ...
      (microsoft.public.dotnet.security)
    • Custom Principal Permission (non-CodeAccessPermission derived) not working
      ... My permission class does not derive from CodeAccessPermission as I am not ... I didn't add the assembly to the Security Policy as MSDN states that it is ... Imperative permission works fine, ... How do I get my Security Attribute derivated class to work? ...
      (microsoft.public.dotnet.security)