IIS doesn't enforce file level NTFS permissions

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi, I've just read
http://www.microsoft.com/technet/pr...technologies/iis/deploy/confeat/permmaze.mspx
and this article doesn't correspond to my testing with IIS on XP Pro, SP2.

I find that when Basic or Integrated Windows auth is applied, only the
permissions of the directory containing the file are interpreted, not the
permissions on the file itself.

That is, if I virtual directory to an NTFS directory with read permissions
for jack and jill, and place a file in that directory with read only for
jill, the following happens:

1. Jack is unable to access the file on disk.
2. Jack is able to access the file over authenticated HTTP.

Is there a setting I can place somewhere that enables fully granular
security for IIS?
 
Douglas wrote on Mon, 5 Feb 2007 02:43:01 -0800:
Hi, I've just read
http://www.microsoft.com/technet/pr...technologies/iis/deploy/confeat/permmaze.mspx
and this article doesn't correspond to my testing with IIS on XP Pro, SP2.

I find that when Basic or Integrated Windows auth is applied, only the
permissions of the directory containing the file are interpreted, not the
permissions on the file itself.

That is, if I virtual directory to an NTFS directory with read permissions
for jack and jill, and place a file in that directory with read only for
jill, the following happens:

1. Jack is unable to access the file on disk.
2. Jack is able to access the file over authenticated HTTP.

Is there a setting I can place somewhere that enables fully granular
security for IIS?
Click to expand...


Did you also disable Anonymous Authentication? If not, the file is being
accessed using the credentials of the IIS anonymous account (normally
IUSR_MACHINENAME) rather than the expected user.

Dan
 
Daniel Crichton said:
Did you also disable Anonymous Authentication?
Click to expand...

Yes. Digest, anonymous and integrated auth are disabled; only basic HTTP
auth is enabled. I'm serving over SSL to Firefox.
 
This turns out to have been sloppy testing on my part; I can't reproduce the
problem anymore.

Daniel, thanks for your help.

Doug
 
Back
Top