[Mono-bugs] [Bug 71366][Nor] Changed - Security exception on running xsp
Tue, 18 Jan 2005 10:01:47 -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 email@example.com.
--- shadow/71366 2005-01-18 09:02:35.000000000 -0500
+++ shadow/71366.tmp.21683 2005-01-18 10:01:47.000000000 -0500
@@ -62,6 +62,27 @@
(Unfortunately the xsp-sample application still does not run.. - but
that's due to another bug)
------- Additional Comments From firstname.lastname@example.org 2005-01-18 09:02 -------
Thanks for the ICU info update - that would have been a hell to find.
+------- Additional Comments From email@example.com 2005-01-18 10:01 -------
+I can't replicate the problem after re-building mono with icu - but I
+may have a different icu than yours. Anyway it seems this is yet
+another case where ICU fails for a most simple test (it's not the first).
+However I the included patch, to Evidence.cs, should avoid calling ICU
+in this case. This should fix your problem - unless you hit other ICU
+Please try this and, if it works, then I'll commit it to SVN.
+As for the Evidence code, it is trigerred because of the new AppDomain
+serialization which "get"s the evidence (and trigger their lazy
+initialization). Normally (within a single AppDomain) the code is
+actually not executed (unless there are some security demands).
+I may change this behaviour soon when SecurityManager.SecurityEnabled
+defaults to false but that would affect other users of evidences :(
+such as isolated storage and XML resolvers.