Hey all,
I'm havin a small 'debate' with one of my IT guys over the possible holes created by giving IUSR write access to an directory in IIS 6 (Directory Browsing is off and was not 'default' install). As I perform file Copies, Deletes and Moves with ASP, I require the entire directory to have write access.
He says that it's a security problem as someone could get in through (what he called) a browser-edit program if they knew the path to the file. Either way, he suggests we only give write access to one specific directory then manipulate the uploads with FTP. He says there are ways for ppl to access/manipulate those files with ISUR write access.
My argument is that you MUST have some kind of server-side script to manipulate the file. My reasoning is that you must create a File Object before you can do anything with it. To do that you A) Need the mapped path on the server and B) need server-side script (residing on the server in question) to manipulate the file.
The company I work for has extremely high security protocols so I can understand the 'better safe than sorry' attitude. I just say he's a little too paranoid.
Any thoughts?
I'm havin a small 'debate' with one of my IT guys over the possible holes created by giving IUSR write access to an directory in IIS 6 (Directory Browsing is off and was not 'default' install). As I perform file Copies, Deletes and Moves with ASP, I require the entire directory to have write access.
He says that it's a security problem as someone could get in through (what he called) a browser-edit program if they knew the path to the file. Either way, he suggests we only give write access to one specific directory then manipulate the uploads with FTP. He says there are ways for ppl to access/manipulate those files with ISUR write access.
My argument is that you MUST have some kind of server-side script to manipulate the file. My reasoning is that you must create a File Object before you can do anything with it. To do that you A) Need the mapped path on the server and B) need server-side script (residing on the server in question) to manipulate the file.
The company I work for has extremely high security protocols so I can understand the 'better safe than sorry' attitude. I just say he's a little too paranoid.
Any thoughts?
