Yep, after doing anything in the registry, I always reboot.

I feel as though I'm miscommunicating. I'm not using IIS, I'm using PWS (Personal Web Server). I realize that these can be considered the same in some respects, but for all I know, that isn't the case here. The only way I've found to manipulate the Script Map is to edit the registry. You mentioned playing with this through the Internet Service Manager - I don't think I have that.

My biggest problem with taking the -T out of the #!, is that it does not appear to be taint checking at all. The code I posted earlier should make taint tell me that it's insecure, but it simply doesn't. This is why I'm going to the trouble of uploading to my webhost to make sure my code runs cleanly in taint.

Update: Due to several complaints, removed signature

Sarah

PWS for NT ships with the Internet Service Manager.

PWS for 98 does not. You're stuck editing the registry. Not only that, but I've seen cases where if you screw up the scriptmap in the registry, you actually have to uninstall/reinstall PWS to get bogus info cleared out of the Metabase (the PWS/IIS settings cache).

I don't know if there's a PWS for 2000. Anyone?

First off, thank you so much for your patience and wisdom, dws, you've solved my problem.

I uninstalled PWS (Win98) and reinstalled. Before rebooting post-installation, I went in and added it to the Script Map with the -T like it should be. After reboot, I tried my make taint puke script and it puked!!! :)

So, for shits and giggles, I uninstalled PWS again, reinstalled and instead of adding perl to the script map with -T, I added it without -T (like so: c:\perl\bin\perl.exe %s %s). After reboot, I modified the entries to include the -T. Rebooted again, and when I tried the script, I got the "Too late for -T" message. Which, was my original problem.

In the end, after fixing then breaking PWS again, I guess the problem was that when setting up PWS for Perl, I didn't think ahead and put the -T where necessary (please, no flames, I was monk-less when I set this up). I'm also an idiot for not test-casing this more simply because if I had mapped .cgit instead of modifying .cgi I most likely would have seen this behavior sooner.

And for the record, now that the problem has been solved, I can safely remove -T from the #! line - it still taint checks.

Update: Due to several complaints, removed signature

Sarah

There isn't PWS for Windows 2000, instead one would install IIS 5.0 - which is included with Windows 2000 Professional.