Title: Message
Only a
perfect coder should use ISAPI filters. If your perl process goes nutty,
haywire, or just plain rampant, then you have quite effectively brought down the
web-server.
It is
also a potential security flaw, ie above situation, but a bad guy decides to
overflow
raw script) is far
easier to work with uncompiled than it is compiled.
Cheers,
Mike Kalinovich
- Original Message -
From: Matthew Greenberg [EMAIL PROTECTED]
To: Harald Wopenka [EMAIL PROTECTED]; Perl-Win32-Users
[EMAIL PROTECTED]
Sent: Thursday, October 31, 2002 10:58 PM
Subject: Re
not contain this
on either server.
Any help would be much appreciated,
Mike Kalinovich
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
. The system environment variables do not contain this
on either server.
Any help would be much appreciated,
Mike Kalinovich
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Now, myself being a Systems administrator, I would be extremely doubtful of
using the simple method of querying the registry. API calls are there for
a reason.
I don't know how easy the registry is to rebuild on W2K, since i haven't had
to do it yet (crosses fingers), but the less playing
I would highly advise reading the MS Support pages, or Technet.
fpsrvadm.exe is the command line utility for FP extensions on NT/W2k. And
Frontpage itself has a permissions tab that you can assign users to. Or you
could always use NTFS permissions.
None of which are Perl based, thus the wrong
If you run the ISAPI version of perl, than it runs under inetinfo.exe, as
would any ISAPI filter installed in IIS.
If you run Perl with the CGI and PL mappings to perl.exe, it can only take
the webserver down if you use a tremendous amount of memory or file handles
(and or threads) to the
