[Mono-devel-list] [PATCH] CAS support with AOT / SecurityManager default to OFF

[Sebastien Pouliot]

Hello,

First, the patch add the missing code to make declarative demands work
with AOT (and fix another previous bug I had with AOT when class could
be uninitialized). This pass all current tests (and my own for
security).

Second, the patch move the SecuirtyManager into unmanaged code and, by
default (i.e. without --security), turns them off.

The properties are moved into unmanaged code for two reasons:

        * some unmanaged code needs to know their status (and it's
        harder/slower to call managed code to get this).
        
        * we don't want applications with the reflection rights to
        change the value (and give themselves all the rights).

without --security

        * SecurityManager.SecurityEnabled is false and cannot be changed
        to true;
        * SecurityManager.CheckExecutionRights is false and cannot be
        changed to true;

with --security

        * SecurityManager.SecurityEnabled is true and can be changed to
        false [1];
        * SecurityManager.CheckExecutionRights is true and can be
        changed to false;


[1] Under the MS runtime (at least for 1.x runtimes) turning off
security is possible but it cannot be turned back on without restarting
the application (but yes you can flip the properties as much as you like
it just wont work ;-).

-- 
Sebastien Pouliot  <sebastien at ximian.com>
blog: http://pages.infinit.net/ctech/poupou.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: corlib.20050121.diff
Type: text/x-patch
Size: 2304 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20050121/91d9602d/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mono.20050121.diff
Type: text/x-patch
Size: 12252 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20050121/91d9602d/attachment-0001.bin