Re: Shared drive VS Security
From: Chris Priede (priede_at_panix.com)
Date: 09/23/05
- Next message: Franz Schenk: "Re: revoking ipsec certificate doesn't work"
- Previous message: Chris Priede: "Re: PCAnywhere port forwarding ?"
- In reply to: Stephan St-Denis: "Re: Shared drive VS Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 23 Sep 2005 04:17:30 -0400
Hi,
Stephan St-Denis wrote:
> So, as I understand this... it seems that the folder in
> which the data is located cannot be hidden from the user. I thought
> there was a way to let an application access a folder but not
> Windows' explorer (e.g. list and access files within that folder).
It depends on how serious your need for security is. If you don't require
real protection and only want to keep the clueless from poking around,
there's a couple things that might help:
1) Put the data on a hidden share (one with a name ending in $) and don't
map it to a drive letter on your clients. Your program should use UNC paths
(e.g. "//server/secret$/"). This will keep users from browsing about and
finding the data, although it won't prevent them from viewing the folder if
they know the UNC path to it. Hopefully your program doesn't display the
path all over...
2) There are also things you can do with the folder's "folder.ini" file
(Google it for more information), to prevent the Windows shell from
displaying its contents. Unfortunately, this won't affect other
applications that can display directory contents, nor will it affect the
command prompt.
-- Chris Priede
- Next message: Franz Schenk: "Re: revoking ipsec certificate doesn't work"
- Previous message: Chris Priede: "Re: PCAnywhere port forwarding ?"
- In reply to: Stephan St-Denis: "Re: Shared drive VS Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|