[Mono-bugs] [Bug 82043][Nor] Changed - WebMethod and PrincipalPermission

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Jul 27 10:20:02 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 atsushi at ximian.com.


--- shadow/82043	2007-07-15 09:10:46.000000000 -0400
+++ shadow/82043.tmp.9219	2007-07-27 10:20:02.000000000 -0400
@@ -10,13 +10,12 @@
 Component: Sys.Web.Services
 AssignedTo: atsushi at ximian.com                            
 ReportedBy: mmorano at mikeandwan.us               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 Summary: WebMethod and PrincipalPermission
 I am trying to secure a simple web service by leveraging the existing forms
 authentication configured for an asp.net site, and was curious if the
 following is expected to work at this point:
@@ -121,6 +120,60 @@
 directory domain, so I dont believe the comments concerned with the
 Name attribute apply here.  Is there something I am missing?
+------- Additional Comments From atsushi at ximian.com  2007-07-27 10:20 -------
+Sebastien, should it work regardless of lacking "mono --security=cas"?
+When I tried below, it got an error, though regardless of the
+[PrincipalPermission] existence:
+atsushi at linux-4gue:~/tests/82403> MONO_OPTIONS=--security=cas xsp2
+Listening on port: 8080 (non-secure)
+Listening on address:
+Root directory: /home/atsushi/tests/82403
+Hit Return to stop the server.
+  at (wrapper managed-to-native)
+System.Security.SecurityFrame._GetSecurityStack (int) <0x00004>
+  at (wrapper managed-to-native)
+System.Security.SecurityFrame._GetSecurityStack (int) <0xffffffff>
+  at System.Security.SecurityFrame.GetStack (int) <0x00037>
+  at System.Threading.CompressedStack.Capture () <0x0003f>
+  at System.Security.SecurityContext.Capture () <0x00075>
+  at System.Threading.ExecutionContext.Capture () <0x00079>
+  at (wrapper runtime-invoke)
+(object,intptr,intptr,intptr) <0xffffffff>
+  at (wrapper managed-to-native)
+(object,intptr) <0x00004>
+  at (wrapper managed-to-native)
+(object,intptr) <0xffffffff>
+  at (wrapper delegate-begin-invoke)
+(System.AsyncCallback,object) <0xffffffff>
+  at System.Net.Sockets.Socket.BeginReceive
+  at System.Net.Sockets.NetworkStream.BeginRead
+(byte[],int,int,System.AsyncCallback,object) <0x00072>
+  at Mono.WebServer.XSPWorker.Run (object) <0x00085>
+  at Mono.WebServer.ApplicationServer.StartRequest
+(System.Net.Sockets.Socket,int) <0x0007f>
+  at Mono.WebServer.ApplicationServer.ReuseSocket
+(System.Net.Sockets.Socket,int) <0x00010>
+  at (wrapper remoting-invoke-with-check)
+(System.Net.Sockets.Socket,int) <0xffffffff>
+  at Mono.WebServer.XSPWorker.Close (bool) <0x000e4>
+  at Mono.WebServer.XSPRequestBroker.Close (int,bool) <0x00046>
+  at (wrapper remoting-invoke-with-check)
+Mono.WebServer.XSPRequestBroker.Close (int,bool) <0xffffffff>
+  at (wrapper xdomain-dispatch) Mono.WebServer.XSPRequestBroker.Close
+(object,byte[]&,byte[]&,int,bool) <0xffffffff>

More information about the mono-bugs mailing list