Unique -- Limiting User to Inside Folder

Unique -- Limiting User to Inside Folder

Secure Home | Search | About
 Microsoft Applications Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Unique -- Limiting User to Inside Folder dw85745 03-07-2008
Posted by dw85745 on March 7, 2008, 7:40 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
I have a program which links to an enterprise server in real-time.

My program uses a DLL provided by the company who owns the server. This DLL
is currently registered in C:\Windows.

============================
My security objective is to keep the server operator from accessing my
system through their DLL (my machine remote access is disabled) if such code
is included within the DLL -- or -- possibly turn on my remote access
remotely (which I understand can be done) even though it is disabled.

If I move the DLL to a specific directory (folder) along with my program,
how do I configure my system so that:

1) I can execute my program as system administrator, and
2) Keep the server provider within the program directory I created without
getting into other directories (folders) or drives on my system.

Thanks
David



Posted by Roger Abell [MVP] on March 8, 2008, 9:17 am
If you were  Registered and logged in, you could reply and use other advanced thread options
It is not possible to answer your questions with the information
that is available. Moving the dll to some other directory will
almost certainly accomplish nothing. If the dll is registered it
could be used by allowed accounts no matter were it is stored
provided only that the attempting account is allowed.
You said your program uses this to access the remote system.
You did not say that your program is running all of the time.
You did not say that anything else uses the code provided by
this company, whether they provided only the dll, whether the
dll is used by svchost to run a service, whether the code binds
to any ports listening for incoming connections, etc..
If you use a cmd prompt and run tasklist /svc is there any
indication that some part of their code is running as a service?
If you at the cmd prompt run netstat -abv is there any sign that
their code is binding to a port as a listener?

Roger

>I have a program which links to an enterprise server in real-time.
>
> My program uses a DLL provided by the company who owns the server. This
> DLL is currently registered in C:\Windows.
>
> ============================
> My security objective is to keep the server operator from accessing my
> system through their DLL (my machine remote access is disabled) if such
> code is included within the DLL -- or -- possibly turn on my remote access
> remotely (which I understand can be done) even though it is disabled.
>
> If I move the DLL to a specific directory (folder) along with my program,
> how do I configure my system so that:
>
> 1) I can execute my program as system administrator, and
> 2) Keep the server provider within the program directory I created
> without getting into other directories (folders) or drives on my system.
>
> Thanks
> David
>
>



Similar ThreadsPosted
folder unique identifier exist? October 5, 2005, 4:08 pm
Limit domain user logon to a unique workstation September 17, 2005, 7:18 pm
Get inside the head of a computer security expert! August 25, 2008, 5:00 pm
Permissions -- Unique Issue July 10, 2008, 12:34 pm
Special folder for user via SID or something like this. August 9, 2005, 10:41 am
Home Folder User Permissions July 26, 2007, 10:06 am
Limiting an account/group to two functions June 28, 2005, 1:01 pm
Limiting the ability to Move Items February 22, 2006, 4:37 pm
Limiting an application's directory access... June 2, 2008, 3:52 am
User sharing personal folder in AD domain July 22, 2005, 2:58 pm

The site map in XML format XML site map

Contact Us | Privacy Policy