Access Rights and Folders
- From: "pgebhard" <pgebhard@xxxxxxxxx>
- Date: 17 Aug 2006 06:18:35 -0700
Hi,
I'm wondering how to expand on the issue dealt with a bit in this
thread:
http://groups.google.com/group/microsoft.public.dotnet.security/browse_thread/thread/cc9121dfe15ef7e2?tvc=2
..
What I want to do is to limit the access control of the app that I
amd working on to only allow it to write in a specific directory
(usually it will just be it's running directory, but maybe it would be
nice to be able to specify a different path either prior to execution
or during runtime). It would be nice to be able to control whether the
app can only read files, or only write files in a particular directory.
You might get my idea...I want to be able to control the app's level
of access.
I've looked a lot into FileIOPermissionAttribute and
FileIOPermission. FileIOPermissionAttribute only seems to let me
assign a minimum level of access rights for the app, but not specify
that I don't want any rights but to a certain directory. Using the
RequestRefuse parameter will refuse rights, but not let me specify that
I want some rights granted, but only to a particular directory. I've
sort of gotten what I want with FileIOPermission and its PermitOnly
method, but when using that, I end up calling it everytime that I make
a call that might write to a file, etc.
So, what are my options? Is there anything that can be done that
would be easy to specify for controling the access rights at the entire
app level?
.
- Prev by Date: Advice requested : Storing SID String in SQL table
- Next by Date: Re: Advice requested : Storing SID String in SQL table
- Previous by thread: Advice requested : Storing SID String in SQL table
- Next by thread: Re: Verify syntax of an URl
- Index(es):
Relevant Pages
|
