Kbase P18260: Why use the cgiip.wsc script with WebSpeed?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
Why use the cgiip.wsc script with WebSpeed?
GOAL:
When to use cgiip executable versus cgiip.wsc?
GOAL:
What is the function of the cgiip.wsc script?
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
IIS
FIX:
Using the cgiip.wsc script is a techniques to minimize unauthorized access to WebSpeed messengers. You can use the sample file cgiip.wsc to set up a file association for running the CGIIP Messenger under Microsoft's IIS Server. For details, see the cgiip.wsc file, which is located in the Progress DLC\bin directory.
Replacing the default filenames and file extensions associated with key WebSpeed files with proprietary (that is, less easily recognizable) names and extensions will limit unauthorized personnel's ability to recognize these files when they display on the URL.
The following list identifies these key files and suggests some ways to shield the identify of each file:
o Rename the default WebSpeed Messenger filename associated with the
messenger type that you are using: cgiip.exe, wsisa.dll, or wsnsa.dll.
o Use a file association technique to shield the identity of the default
WebSpeed Messenger and Broker filenames when they are run.
This activity is only supported if you are using a Microsoft Internet
Information Web Server (ISS Web Server) on a Windows NT platform,
and your WebSpeed Messenger type is cgiip.exe.
o This technique allows you to define a file extension that can run an
executable. The file extension, which includes the default filenames
of the WebSpeed Messenger and Broker, obscures the identity of these
files as it passes the Broker name to an executable that runs them.
NOTE: You must restart an ISAPI or Netscape NSAPI Web server after installing and configuring the Messenger