|
|
You're in the
iis security
group:file extensions and IIS
iis security:
I'm wondering which file extensions are treated as "exposed" and which are "hidden" by the IIS? I was told that the .bak file is exposed so external users can actually browse and see content of files with .bak extension but I couldn't reproduce it. Thanks for your advice and pointers.
[quoted text, click to view]
On Nov 1, 3:20 pm, "Zester" <z...@nottospam.com> wrote: > Hi, > > I'm wondering which file extensions are treated as "exposed" and which are > "hidden" by the IIS? I was told that the .bak file is exposed so external > users can actually browse and see content of files with .bak extension but I > couldn't reproduce it. Thanks for your advice and pointers. IIS does not treat file extensions as "hidden" or "exposed". So, the behavior of .bak file that you describe does not exist, and I don't really know what you are trying to reproduce. What IIS *does* do is route all requests by file extension to be "handled" (i.e. processed) by something. That something is called a "handler", and the handler decides what to do with the resource. It sounds like you want to make a directory browseable and .bak files downloadable, which means you want to enable Directory Browsing for a directory and set a MIME Type for the .bak extension to enable its contents to be browsed and seen by a browsing user. Please search for documentation on "Directory Browsing" and "MIME Type" on how to accomplish them. If they are not what you want, please describe further what behavior you want. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //
No, that wasn't what I was looking for. I'm concerned about the security
risk of exposing content of files that we didn't intend to. The .bak file might be a web.config.bak that contains some sensitive info; I don't want users to have access to it. [quoted text, click to view] "David Wang" <w3.4you@gmail.com> wrote in message news:1193981533.581025.25860@q3g2000prf.googlegroups.com... > On Nov 1, 3:20 pm, "Zester" <z...@nottospam.com> wrote: >> Hi, >> >> I'm wondering which file extensions are treated as "exposed" and which >> are >> "hidden" by the IIS? I was told that the .bak file is exposed so external >> users can actually browse and see content of files with .bak extension >> but I >> couldn't reproduce it. Thanks for your advice and pointers. > > > > IIS does not treat file extensions as "hidden" or "exposed". > > So, the behavior of .bak file that you describe does not exist, and I > don't really know what you are trying to reproduce. > > What IIS *does* do is route all requests by file extension to be > "handled" (i.e. processed) by something. That something is called a > "handler", and the handler decides what to do with the resource. > > It sounds like you want to make a directory browseable and .bak files > downloadable, which means you want to enable Directory Browsing for a > directory and set a MIME Type for the .bak extension to enable its > contents to be browsed and seen by a browsing user. > > Please search for documentation on "Directory Browsing" and "MIME > Type" on how to accomplish them. If they are not what you want, please > describe further what behavior you want. > > > //David > http://w3-4u.blogspot.com > http://blogs.msdn.com/David.Wang > // >
Ok, I see.
The behavior of IIS completely depends on its configuration, and it can be configured to do what you say, or not what you want. There is no feature which says "hide or expose resources by extension". However, it is possible to hide or expose resources by extension with a combination of configuration. Thus, one needs to know the IIS version, the MIME Type, and Application Mapping configuration which applies to the URL in question. Prior to IIS6, default configuration would allow .bak to be downloaded, while IIS6 and later would not allow .bak to be downloaded. And of course, there are many ways to configure IIS to do the opposite of its defaults. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang // [quoted text, click to view] On Nov 2, 9:31 am, "Zester" <z...@nottospam.com> wrote: > No, that wasn't what I was looking for. I'm concerned about the security > risk of exposing content of files that we didn't intend to. The .bak file > might be a web.config.bak that contains some sensitive info; I don't want > users to have access to it. > > "David Wang" <w3.4...@gmail.com> wrote in message > > news:1193981533.581025.25860@q3g2000prf.googlegroups.com... > > > > > On Nov 1, 3:20 pm, "Zester" <z...@nottospam.com> wrote: > >> Hi, > > >> I'm wondering which file extensions are treated as "exposed" and which > >> are > >> "hidden" by the IIS? I was told that the .bak file is exposed so external > >> users can actually browse and see content of files with .bak extension > >> but I > >> couldn't reproduce it. Thanks for your advice and pointers. > > > IIS does not treat file extensions as "hidden" or "exposed". > > > So, the behavior of .bak file that you describe does not exist, and I > > don't really know what you are trying to reproduce. > > > What IIS *does* do is route all requests by file extension to be > > "handled" (i.e. processed) by something. That something is called a > > "handler", and the handler decides what to do with the resource. > > > It sounds like you want to make a directory browseable and .bak files > > downloadable, which means you want to enable Directory Browsing for a > > directory and set a MIME Type for the .bak extension to enable its > > contents to be browsed and seen by a browsing user. > > > Please search for documentation on "Directory Browsing" and "MIME > > Type" on how to accomplish them. If they are not what you want, please > > describe further what behavior you want. > > > //David > >http://w3-4u.blogspot.com > >http://blogs.msdn.com/David.Wang > > //- Hide quoted text - > > - Show quoted text -
Is there a way to audit which files are allowed to be downloaded by default
configuration? I looked into IIS5 Application Configuration dialog and didn't see .bak to be in the mapping for the website but it was allowed to be downloaded as you pointed out. IIS6 doesn't have the entry either but it's not allowed to be downloaded. Sounds like the default configuration is hidden. Also, would you know a documentation that walks me through how to block .bak from being downloaded in IIS5? Thanks! [quoted text, click to view] "David Wang" <w3.4you@gmail.com> wrote in message news:1194058410.973691.294860@e9g2000prf.googlegroups.com... > Ok, I see. > > The behavior of IIS completely depends on its configuration, and it > can be configured to do what you say, or not what you want. There is > no feature which says "hide or expose resources by extension". > However, it is possible to hide or expose resources by extension with > a combination of configuration. > > Thus, one needs to know the IIS version, the MIME Type, and > Application Mapping configuration which applies to the URL in > question. > > Prior to IIS6, default configuration would allow .bak to be > downloaded, while IIS6 and later would not allow .bak to be > downloaded. And of course, there are many ways to configure IIS to do > the opposite of its defaults. > > > //David > http://w3-4u.blogspot.com > http://blogs.msdn.com/David.Wang > // > > > > > > > > On Nov 2, 9:31 am, "Zester" <z...@nottospam.com> wrote: >> No, that wasn't what I was looking for. I'm concerned about the security >> risk of exposing content of files that we didn't intend to. The .bak file >> might be a web.config.bak that contains some sensitive info; I don't want >> users to have access to it. >> >> "David Wang" <w3.4...@gmail.com> wrote in message >> >> news:1193981533.581025.25860@q3g2000prf.googlegroups.com... >> >> >> >> > On Nov 1, 3:20 pm, "Zester" <z...@nottospam.com> wrote: >> >> Hi, >> >> >> I'm wondering which file extensions are treated as "exposed" and which >> >> are >> >> "hidden" by the IIS? I was told that the .bak file is exposed so >> >> external >> >> users can actually browse and see content of files with .bak extension >> >> but I >> >> couldn't reproduce it. Thanks for your advice and pointers. >> >> > IIS does not treat file extensions as "hidden" or "exposed". >> >> > So, the behavior of .bak file that you describe does not exist, and I >> > don't really know what you are trying to reproduce. >> >> > What IIS *does* do is route all requests by file extension to be >> > "handled" (i.e. processed) by something. That something is called a >> > "handler", and the handler decides what to do with the resource. >> >> > It sounds like you want to make a directory browseable and .bak files >> > downloadable, which means you want to enable Directory Browsing for a >> > directory and set a MIME Type for the .bak extension to enable its >> > contents to be browsed and seen by a browsing user. >> >> > Please search for documentation on "Directory Browsing" and "MIME >> > Type" on how to accomplish them. If they are not what you want, please >> > describe further what behavior you want. >> >> > //David >> >http://w3-4u.blogspot.com >> >http://blogs.msdn.com/David.Wang >> > //- Hide quoted text - >> >> - Show quoted text - > >
I'm taking the no response as there is no way to perform the audit [sigh]
This is how a security hole can become a big nasty hole because it gives users a false sense of security. Who knows which sensitive files out there are being exposed to hackers because of the lack of this audit feature! [quoted text, click to view] "Zester" <zeze@nottospam.com> wrote in message news:%23wBYHs9HIHA.3400@TK2MSFTNGP03.phx.gbl... > Is there a way to audit which files are allowed to be downloaded by > default configuration? I looked into IIS5 Application Configuration dialog > and didn't see .bak to be in the mapping for the website but it was > allowed to be downloaded as you pointed out. IIS6 doesn't have the entry > either but it's not allowed to be downloaded. Sounds like the default > configuration is hidden. > > Also, would you know a documentation that walks me through how to block > .bak from being downloaded in IIS5? Thanks! > > > > "David Wang" <w3.4you@gmail.com> wrote in message > news:1194058410.973691.294860@e9g2000prf.googlegroups.com... >> Ok, I see. >> >> The behavior of IIS completely depends on its configuration, and it >> can be configured to do what you say, or not what you want. There is >> no feature which says "hide or expose resources by extension". >> However, it is possible to hide or expose resources by extension with >> a combination of configuration. >> >> Thus, one needs to know the IIS version, the MIME Type, and >> Application Mapping configuration which applies to the URL in >> question. >> >> Prior to IIS6, default configuration would allow .bak to be >> downloaded, while IIS6 and later would not allow .bak to be >> downloaded. And of course, there are many ways to configure IIS to do >> the opposite of its defaults. >> >> >> //David >> http://w3-4u.blogspot.com >> http://blogs.msdn.com/David.Wang >> // >> >> >> >> >> >> >> >> On Nov 2, 9:31 am, "Zester" <z...@nottospam.com> wrote: >>> No, that wasn't what I was looking for. I'm concerned about the security >>> risk of exposing content of files that we didn't intend to. The .bak >>> file >>> might be a web.config.bak that contains some sensitive info; I don't >>> want >>> users to have access to it. >>> >>> "David Wang" <w3.4...@gmail.com> wrote in message >>> >>> news:1193981533.581025.25860@q3g2000prf.googlegroups.com... >>> >>> >>> >>> > On Nov 1, 3:20 pm, "Zester" <z...@nottospam.com> wrote: >>> >> Hi, >>> >>> >> I'm wondering which file extensions are treated as "exposed" and >>> >> which >>> >> are >>> >> "hidden" by the IIS? I was told that the .bak file is exposed so >>> >> external >>> >> users can actually browse and see content of files with .bak >>> >> extension >>> >> but I >>> >> couldn't reproduce it. Thanks for your advice and pointers. >>> >>> > IIS does not treat file extensions as "hidden" or "exposed". >>> >>> > So, the behavior of .bak file that you describe does not exist, and I >>> > don't really know what you are trying to reproduce. >>> >>> > What IIS *does* do is route all requests by file extension to be >>> > "handled" (i.e. processed) by something. That something is called a >>> > "handler", and the handler decides what to do with the resource. >>> >>> > It sounds like you want to make a directory browseable and .bak files >>> > downloadable, which means you want to enable Directory Browsing for a >>> > directory and set a MIME Type for the .bak extension to enable its >>> > contents to be browsed and seen by a browsing user. >>> >>> > Please search for documentation on "Directory Browsing" and "MIME >>> > Type" on how to accomplish them. If they are not what you want, please >>> > describe further what behavior you want. >>> >>> > //David >>> >http://w3-4u.blogspot.com >>> >http://blogs.msdn.com/David.Wang >>> > //- Hide quoted text - >>> >>> - Show quoted text - >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |