Re: Is it possible to adjust security for a networked assembly from app.config?

From: Nicole Calinoiu (calinoiu)
Date: 11/16/05 

Date: Wed, 16 Nov 2005 11:58:03 -0500

Your assemblies will need to be granted OleDbPermission in order for this
code to run. In addition, if this is running on the v. 1.x .NET Framework,
at least the assembly in which your Stitch.Database.DBConnection type
resides will need to be granted unrestricted permissions (aka "full trust")
due to link demands placed on the System.Data.OleDb types. (However, that's
presumably already done since that the OleDbConnection.Open method actually
gets called.)

"Brad Wood" <bradley|.wood|@ndsu|.edu> wrote in message
news:%23LlpMRW6FHA.2524@TK2MSFTNGP10.phx.gbl...
> Sorry; was at a conference last week. Following is the stack:
>
> System.Security.SecurityException: Request failed.
> at
> System.Security.CodeAccessSecurityEngine.CheckSetHelper(PermissionSet
> grants, PermissionSet denied, PermissionSet demands)
> at System.Security.CodeAccessSecurityEngine.CheckSet(PermissionSet
> permSet, StackCrawlMark& stackMark, Int32 checkFrames, Int32
> unrestrictedOverride)
> at System.Security.CodeAccessSecurityEngine.Check(PermissionSet
> permSet, StackCrawlMark& stackMark)
> at System.Security.PermissionSet.Demand()
> at System.Data.OleDb.OleDbConnectionString.Demand(OleDbConnectionString
> constr)
> at System.Data.OleDb.OleDbConnection.Open()
> at Stitch.Database.DBConnection..ctor(DatabaseType Type, String Path)
> at NDSU.ProgressTracker.Persister.init()
>
> Nicole Calinoiu wrote:
>> If you're using an Access application via ADO.NET, you're probably seeing
>> problems due to the permissions required by the ADO.NET provider, not the
>> file permissions. Could you please provide the full details of the
>> exception you're seeing (incl. call stack), as returned from its
>> ToString() method?

Relevant Pages

  • Re: Reason behind implicit FullTrust LinkDemand?
    ... The removal of permissions from the Internet Zone or the ... time to protect the System* assemblies from this attack. ... the security holes are patched. ... The knew the LinkDemand would be a fix. ...
    (microsoft.public.dotnet.security)
  • Reason behind implicit FullTrust LinkDemand?
    ... The .NET Framework assemblies ... One may counter argue that the implicit FullTrust ... LinkDemand just forces users to grant full trust to code that doesn't really ... permissions describing custom actions allowed or not in the system. ...
    (microsoft.public.dotnet.security)
  • Re: security/strong name/zones clarification needed
    ... Was this also true in the Intranet Zone? ... >child code-group with full permissions granted to any ... >> needs to host the CLR, it creates an AppDomain, but due ... All my assemblies are strong named. ...
    (microsoft.public.dotnet.security)
  • Re: security/strong name/zones clarification needed
    ... several but not publicly documented) about child code-group permissions ... a strong-name, or Authenticode signature evidence. ... This problem would also crop up in the AppDomain case also. ... All my assemblies are strong named. ...
    (microsoft.public.dotnet.security)
  • Re: security/strong name/zones clarification needed
    ... > this AppDomain needs to be setup before your assembly can be loaded, ... > Your assembly will have enough permissions, ... When the call stack is initiated, ... All my assemblies are strong named. ...
    (microsoft.public.dotnet.security)
Quantcast