Home All Groups Group Topic Archive Search About

Ent. Library w/DB 2 registry access problem

Author
16 Mar 2006 4:47 PM
slpg5250
Hi,
We are using Enteprise library in our application to manage database
connectivity to a DB2 server. When the application is delpoyed we receive an
error when opening a connection to the database. The problem is that the
db2app.dll is not allowed the registry access. I have read the security
policy documents and have generated a policy file with Enterprise level
permission with unrestricted registry access. Yet, still this does not give
it the appropriate permissions. If the code uses a managed Db2 connection it
works fine. Has anyone ever encountered this problem and/or does anyone have
a fix for this? Thank you.

Author
16 Mar 2006 7:21 PM
Joe Kaplan (MVP - ADSI)
Is the registry access due to a Windows ACL problem or a CAS problem?  If it
is Windows ACL, then CAS policy won't help you.  CAS can only further
restrict what Windows can do in the first place.

Do you know what registry keys are being accessed and what their permissions
are?

Joe K.

Show quoteHide quote
"slpg5250" <slpg5***@discussions.microsoft.com> wrote in message
news:0ACB93BB-31EE-40C0-BAFB-8DBAC721C53D@microsoft.com...
> Hi,
> We are using Enteprise library in our application to manage database
> connectivity to a DB2 server. When the application is delpoyed we receive
> an
> error when opening a connection to the database. The problem is that the
> db2app.dll is not allowed the registry access. I have read the security
> policy documents and have generated a policy file with Enterprise level
> permission with unrestricted registry access. Yet, still this does not
> give
> it the appropriate permissions. If the code uses a managed Db2 connection
> it
> works fine. Has anyone ever encountered this problem and/or does anyone
> have
> a fix for this? Thank you.
>
Author
16 Mar 2006 6:26 PM
Dominick Baier [DevelopMentor]
> CAS can only
> further restrict what Windows can do in the first place.


well - to be exact -

CAS comes first, then Windows :))

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

Show quoteHide quote
> Is the registry access due to a Windows ACL problem or a CAS problem?
> If it is Windows ACL, then CAS policy won't help you.  CAS can only
> further restrict what Windows can do in the first place.
>
> Do you know what registry keys are being accessed and what their
> permissions are?
>
> Joe K.
>
> "slpg5250" <slpg5***@discussions.microsoft.com> wrote in message
> news:0ACB93BB-31EE-40C0-BAFB-8DBAC721C53D@microsoft.com...
>
>> Hi,
>> We are using Enteprise library in our application to manage database
>> connectivity to a DB2 server. When the application is delpoyed we
>> receive
>> an
>> error when opening a connection to the database. The problem is that
>> the
>> db2app.dll is not allowed the registry access. I have read the
>> security
>> policy documents and have generated a policy file with Enterprise
>> level
>> permission with unrestricted registry access. Yet, still this does
>> not
>> give
>> it the appropriate permissions. If the code uses a managed Db2
>> connection
>> it
>> works fine. Has anyone ever encountered this problem and/or does
>> anyone
>> have
>> a fix for this? Thank you.