J
John Heitmuller.
Conceptually, what is the best approach here?
I am implementing a public website in the following environment.
• Windows 2003 Server w/ IIS 6.
• Anonymous access enabled via the IUSR_machinename account.
• Classic .asp fro server side scripting
I have a small encrypted data file in the root directory of the
website. Right now if the user enters the url into their browser
http://www.mypublicdomain.com/myencrytedfile.dat the user can download
the encrypted file.
The .asp scripts need access to the encrypted file. I am assuming
that the .asp scripts are running under the IUSR_machinename account.
I need to be able to allow my .asp scripts to access the file, while
preventing anonymous users from seeing (and downloading) the file.
If I can get pointed in the right direction I think I can work out the
details.
Thanks,
John
I am implementing a public website in the following environment.
• Windows 2003 Server w/ IIS 6.
• Anonymous access enabled via the IUSR_machinename account.
• Classic .asp fro server side scripting
I have a small encrypted data file in the root directory of the
website. Right now if the user enters the url into their browser
http://www.mypublicdomain.com/myencrytedfile.dat the user can download
the encrypted file.
The .asp scripts need access to the encrypted file. I am assuming
that the .asp scripts are running under the IUSR_machinename account.
I need to be able to allow my .asp scripts to access the file, while
preventing anonymous users from seeing (and downloading) the file.
If I can get pointed in the right direction I think I can work out the
details.
Thanks,
John