1

Topic: The security arrangement.Net - whether is live?

Here it is interesting, whether whether it is live and  someone? What it is necessary to know, if your library does not use critical operations and you would like, that it could  without recompilation in systems restricted safety? Only to put down assembly: AllowPartiallyTrustedCallers? Here, I look one of popular linguistic data bases: #if (! NETCF)////If log4net is strongly named it still allows partially trusted callers//[assembly: System.Security.AllowPartiallyTrustedCallers] #endif #if (NET_4_0)////Allows partial trust applications (e.g. ASP.NET shared hosting) on.NET 4.0 to work//given our implementation of ISerializable.//[assembly: System. Security. SecurityRules (System. Security. SecurityRuleSet. Level1)] #endif CF died, therefore, it turns out, AllowPartiallyTrustedCallers we put for all. And here the second line as I understood, translates the project to the old circuit of check by safety. In general, what can tell about it? If at you library and you think that it does not use SecuritySritical that you need to make? Z.Y.earlier always put AllowPartiallyTrustedCallers and  a program, launches other programs with the restricted rights http://managedsandbox.codeplex.com/

2

Re: The security arrangement.Net - whether is live?

Hello, Shmj, you wrote: S> in general, what can tell about it? If at you library and you think that it does not use SecuritySritical that you need to make? Both in IIS and on a desktop without any attributes in partial trusted env any code without knee-bends with attributes works. What exactly confuses?

3

Re: The security arrangement.Net - whether is live?

Hello, VladCore, you wrote: VC> Both in IIS and on a desktop without any attributes in partial trusted env any code without knee-bends with attributes works. And how you checked? By default IIS restricts the rights only at the expense of the trimmed rights of the user under which works.