[Mono-bugs] [Bug 52606][Wis] Changed - Code access security implementation

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 3 Feb 2005 10:15:43 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien@ximian.com.


--- shadow/52606	2005-01-22 11:35:45.000000000 -0500
+++ shadow/52606.tmp.16723	2005-02-03 10:15:43.000000000 -0500
@@ -1,12 +1,12 @@
 Bug#: 52606
 Product: Mono: Runtime
 Version: unspecified
 OS: other
 OS Details: 
-Status: NEW   
+Status: ASSIGNED   
 Severity: Unknown
 Priority: Wishlist
 Component: misc
 AssignedTo: sebastien@ximian.com                            
 ReportedBy: lupus@ximian.com               
@@ -31,6 +31,32 @@
 * Most *Permission and *PermissionAttribute classes are now
 implemented. Most MSDN library samples are now working correctly
 (unless they use non-implemented features). 
 * Added dependency on #62358 "MCS doesn't encode SecurityAttributes
+------- Additional Comments From sebastien@ximian.com  2005-02-03 10:15 -------
+** Status update **
+Mono 1.1.4 supports the --security option to enable the security manager.
+What's supported
+- Policy resolution - including RequestMinimum, RequestOptional and
+- Declarative/Imperative demands;
+- Declarative stack modifiers (Assert, Deny and PermitOnly);
+What's not (yet) supported
+- LinkDemand (jit time) and it's special cases (icalls, pinvoke, APTC);
+- InheritanceDemand (load time);
+- Imperative stack modifiers (Assert, Deny and PermitOnly);
+- RequestMinimum is only evaluated at policy resolution - not at
+assembly load time;
+- Stack propagation for Thread, Async ...;
+- Cross-AppDomain support;
+Note: Although the CAS infrastructure is in place, the class libraries
+have not yet been audited and properly tagged for CAS use, this work
+is just starting. Some of this work will not be visible until the
+audit is complete.