RE: Controlling access to pdf/doc files

["Harper.Matthew" <Matthew.Harper () SunTrust com>]

I agree with below.  There is really no valid reason (save for a few
"reference" .pdf or .docs) to create a large amount of files containing
confidential information and store them on a server.  The best solution
is to dynamically generate them as noted below and load into the client
side cache there-by never storing it on the server side.

The only draw back to above is you now have a .pdf or .doc sitting in
the clients internet cache folder.  If the client machine is not
configured to delete that cache on a normal bases or the client doesn't
do it on there own, any person with elevated rights to the client
machine could browse the cache folder and view the cached .pdf or .doc
file.   This is not really a huge issue with home users but is an issue
with kiosk machines, etc..

Matthew. 

-----Original Message-----
From: Jed Holler [mailto:j.holler () juno com] 
Sent: Tuesday, February 24, 2004 3:59 PM
To: webappsec () securityfocus com
Subject: Re: Controlling access to pdf/doc files


I think it may be better to have the file dynamically generated, and
then deleted as soon as the file is transferred. Have the file name be a
random number or string, generated by your application. Also set a timer
that will delete the file after 2 or 3 minutes, in case the client
terminates the connection before the file has a chance to transfer.

Jed

________________________________________________________________
The best thing to hit the Internet in years - Juno SpeedBand! Surf the
Web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to
sign up today!