Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Smart Client Software Factory Security Problems With Partially Trusted Callers
Source: Microsoft Support
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Smart client application development for partially trusted environment, using both the
May 2007 Smart Client Software Development Factory
(http://msdn2.microsoft.com/en-us/library/aa480482.aspx)
and the
Enterprise Library Edition 3.1
(http://www.microsoft.com/downloads/details.aspx?familyid=4C557C63-708F-4280-8F0C-637481C31718&displaylang=en)
.
System.Security.SecurityException was unhandled
 Message="That assembly does not allow partially trusted callers."
The SmartClient Software Factory was never intended to run in a partially trusted context or environment. Thus, it may contain strong-name-signed assemblies that are not decorated with the AllowPartiallyTrustedCallers attribute. Strong-named assemblies have a LinkDemand for full-trust, which will cause a SecurityException on partially-trusted callers when the AllowPartiallyTrustedCaller attribute is not applied to the strong-name-signed assembly.
The Smart Client Software Factory was never intended for use in a partially-trusted environment. i.e., it does not use the AllowPartiallyTrustedCallers attribute.
The Enterprise Library 3.1 does have support for partially trusted callers, but has a known bug in the ObjectBuild assembly, which does not have the AllowPartiallyTrustedCallers attribute.
CodePlex
(http://www.codeplex.com/CodePlex)
Â
Creating an AppDomain with limited permissions
(http://blogs.msdn.com/shawnfa/archive/2004/10/25/247379.aspx)
An Enhanced Version of the Sandboxed AppDomain
(http://blogs.msdn.com/shawnfa/archive/2004/11/02/251239.aspx)
How to: Debug a Partial Trust Application
(http://msdn2.microsoft.com/en-us/library/ms164730.aspx)
Exception Assistant
(http://msdn2.microsoft.com/en-us/library/197c1fsc.aspx)
Â
Giving the application Full-Trust is not the same as giving permissions with all the predefined permissions sets (Everything).Â
CLR Integration Code Access Security
(http://msdn2.microsoft.com/en-us/library/ms345101.aspx)
FullTrust means Full Trust
(http://blogs.msdn.com/eugene_bobukh/archive/2005/05/06/415217.aspx)
The Security Infrastructure of the CLR Provides Evidence, Policy, Permissions, and Enforcement Services
(http://msdn2.microsoft.com/en-us/magazine/cc188939.aspx)
Patch for Partial Trust support in Enterprise Library for .NET 2.0
(http://blogs.msdn.com/tomholl/archive/2006/06/30/652955.aspx)
Whidbey's New SecurityException
(http://blogs.msdn.com/shawnfa/archive/2004/07/30/202468.aspx)
Using CasPol to Fully Trust a Share
(http://blogs.msdn.com/shawnfa/archive/2004/12/30/344554.aspx)
Â
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALSâ€) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Article ID: 951981 - Last Review: April 21, 2008 - Revision: 1.2
APPLIES TO
- Microsoft .NET Framework 1.0
- Microsoft .NET Framework 1.0 Service Pack 3
- Microsoft .NET Framework 1.1 Device Update 3.0
- Microsoft .NET Framework 1.1 Service Pack 1
- Microsoft .NET Framework 2.0
- Microsoft .NET Framework 2.0 IA64 Edition
- Microsoft .NET Framework 2.0 Service Pack 1 (x86)
- Microsoft .NET Framework 2.0 Software Development Kit
- Microsoft .NET Framework 2.0 x64 Edition
- Microsoft .NET Framework 3.0
- Microsoft .NET Framework 3.5
- Microsoft .NET Framework Class Libraries 2.0
- Microsoft .NET Framework 1.1
- Microsoft ASP.NET 1.1
| kbnomt kbrapidpub KB951981 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate