[Mono-bugs] [Bug 81133][Wis] Changed - mono --security throws System.NullReferenceException

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Mar 13 22:39:16 EDT 2007

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 at ximian.com.


--- shadow/81133	2007-03-13 20:32:28.000000000 -0500
+++ shadow/81133.tmp.8177	2007-03-13 21:39:16.000000000 -0500
@@ -1,16 +1,16 @@
 Bug#: 81133
-Product: Mono: Class Libraries
+Product: Mono: Runtime
 Version: 1.2
+OS: unknown
 OS Details: Debian Etch, kernel, x86_64
 Status: NEW   
-Priority: Major
-Component: System.Security
+Severity: Unknown
+Priority: Wishlist
+Component: misc
 AssignedTo: sebastien at ximian.com                            
 ReportedBy: michael at ynet.sk               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -67,6 +67,31 @@
 Additional Information:
 In fact I need security manager for real project not for this test. I am
 using in .NET PrincipalPermission attribute in this usage:
 [PrincipalPermission(SecurityAction.Demand, Role = "test")] as critical
 part of remote proxy security.
+------- Additional Comments From sebastien at ximian.com  2007-03-13 21:39 -------
+Downgrading priority. Please note that the security manager is
+*experimental* (i.e. not supported) and provided only as a preview in
+Mono 1.2.
+I don't have a x64 to test this myself (it works on my x86) but it
+looks like monobuild x64 (sles9) doesn't have this issue using SVN HEAD
+I'm not sure which version of mono you are using but:
+- there was a regression in the stack walking code just before the
+last release (but I'm pretty sure it didn't break this test);
+- bug #80936 also limited the use of PrincipalPermission (again this
+never affect this particular test case).
+Both issues will be fixed in the next Mono release but the security
+manager is (and stays) experimental and unsupported - i.e. it
+shouldn't be used for a "critical part" of anything.
+In this particular case, non-CAS permission, the use of imperative
+security (source) instead of declarative security (attribute) should
+work (in a non-experimental and supported way).

More information about the mono-bugs mailing list