Groups | Blog | Home
all groups > iis security > july 2003 >

iis security : CGI Script permissions


Mike Garner
7/28/2003 3:51:57 PM
I've been tasked with the job of migrating an iPlanet Web
Server to IIS 6.0. I wrote nearly all of the CGI on the
server so I've got a pretty good handle on what its
trying to do. There are several scripts that provide web-
based utilities, to read directories, set permissions,
etc. within the wwwroot. For example, the script will
get a directory listing of all the subdirs in a given
directory and print those back to the browser. When this
CGI script (written in PERL) runs on the IIS 6.0 machine,
none of the directories get printed. The same script
executed locally on the server via command line works
fine. Other functions of CGI seem to work ok,
interfacing with a MySQL database, formmailers, etc. But
when a script needs to create a file on the server, or in
similar filesystem/operating system interactions, this
external process doesn't take place. What do I need to
allow for this to work? On the cgi-bin virtual directory
I've permitted all the checkboxes, but that didn't seem
to help: Script Source Access, Read, Write, Directory
Browsing, Log visits, Index this resouce.

Thanks in advance,
Mike Garner
7/28/2003 8:43:47 PM
Everything looks normal. I'm not terribly familiar with
the IIS interface so I haven't looked at the logs (not
really sure where to find those yet). I'll dig around a
bit but for the most part the HTML output is as expected
except the parts that are missing that should be command
line output trapped by Perl variables. In those cases,
the variables are null so its as if the system calls
weren't executed at all..


[quoted text, click to view]
Bernard
7/29/2003 11:01:21 AM
Is there any error msgs ?
what's the http status reply for that request in IIS log ?

--
Regards,
Bernard Cheah
http://support.microsoft.com/
Please respond to newsgroups only ...


[quoted text, click to view]

Bernard
7/29/2003 12:11:00 PM
default log path is at
%windir%/system32/logfiles/w3svcX
x - is the site ID.

without error msgs hard to trace... you might want to
put in some debug code.. say 'print' something on the page
for each steps.. step1 - do this.. step 2.. do that..

hopefully from there, you can further isolate the problem
section.


--
Regards,
Bernard Cheah
http://support.microsoft.com/
Please respond to newsgroups only ...


[quoted text, click to view]

AddThis Social Bookmark Button