Re: write permissions for IISFrom: Arvind Shyamsundar (email@example.com)
- Previous message: Bryan Ponnwitz: "Re: Terminal Services Auditing not working"
- Maybe in reply to: Matej Pfajfar: "write permissions for IIS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 20 Jul 2002 17:41:48 -0000 From: Arvind Shyamsundar <firstname.lastname@example.org> To: email@example.com('binary' encoding is not supported, stored as-is) In-Reply-To: <firstname.lastname@example.org>
If I may summarize it looks as though
- your software (ASP pages) accept some requests from the web
- the ASP dynamically generates the Word DOC file
- saves this DOC to a VDIR
- the client later downloads this DOC from the VDIR using a straight HTTP
Based on the above I see the following potential threats:
- that VDIR would have to have WRITE permission for IUSR_<machine> at the
NTFS level; which is a potentially bad idea
- no access control would be enforced on the downloads; meaning users can
potentially lift off other's files
My recommendation would therefore be
- use the ASP page to write the binary stream with appropriate HTTP
headers so that the browser prompts to download the DOC
- thereby no extra directory would be needed etc.
- the drawback is obviously more computation at each request.
Alternatively one can use a out-of-process COM / COM+ application to
create and retrieve these DOC files, thereby
- using DCOMcnfg or equivalent (MTS package identity) can run as non
- enforcing access control; the COM component would use some session token
to restrict access to only the user's files
- non-compute intensive; the content creation can be done offline and not
on each request.
- the out of process execution of the COM server would avoid direct WRITE
permissions being required.
Brainbench MVP for Internet Security