Re: AddDomain with FullTrust
From: Joel Lucsy (jjlucsy_at_usol.com)
Date: 03/04/05
- Next message: Valery Pryamikov: "Re: DESCryptoServiceProvider"
- Previous message: kurbylogic_at_hotmail.com: "Re: Assembly.Load fails after assembly preloaded using Assembly.LoadFrom (v1.1.4322)"
- In reply to: kurbylogic_at_hotmail.com: "Re: AddDomain with FullTrust"
- Next in thread: kurbylogic_at_hotmail.com: "Re: AddDomain with FullTrust"
- Reply: kurbylogic_at_hotmail.com: "Re: AddDomain with FullTrust"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 04 Mar 2005 15:09:58 -0500
kurbylogic@hotmail.com wrote:
> The short answer is yes.
> - Kurt
>
Well, in short, you're wrong, or at least I'm not seeing the behavior
you described. The unmanaged host shows the exact same behavior as
running the assembly directly, i.e. it throws a security exception for
the native p/invoked library. If I grant the right zone permissions,
both work, managed and unmanaged.
I could be writing the unmanaged host wrong, but I'm not seeing a full
trust/no trust dichotomy. I'm doing the standard CorBindToRuntime,
CreateDomain,ExecuteAssembly. I'm suspecting that I need to create the
Evidence, or perhaps SetAppDomainPolicy, but so far I can't get it work.
So, does anyone have any examples of "opening" the permissions instead
of further restricting them?
-- Joel Lucsy "The dinosaurs became extinct because they didn't have a space program." -- Larry Niven
- Next message: Valery Pryamikov: "Re: DESCryptoServiceProvider"
- Previous message: kurbylogic_at_hotmail.com: "Re: Assembly.Load fails after assembly preloaded using Assembly.LoadFrom (v1.1.4322)"
- In reply to: kurbylogic_at_hotmail.com: "Re: AddDomain with FullTrust"
- Next in thread: kurbylogic_at_hotmail.com: "Re: AddDomain with FullTrust"
- Reply: kurbylogic_at_hotmail.com: "Re: AddDomain with FullTrust"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]