Technical article 105777

How do I configure InterScan VirusWall to scan HTTP files real-time?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4

Written · Last revised

Problem

Are there any documents (printed or online) that discuss how to
configure VirusWall to scan http files?  The VirusWall configuration
URL page does not have an option to configure HTTP, which is
accessed via http://<Host_Name>:1812/scancfg?69,13.  How do I
configure Interscan VirusWall to scan HTTP files real-time?

Cause

No documentation exists to explain how to configure VirusWall HTTP
real-time scanning and the VirusWall configuration page is missing
an http option.  The /etc/iscan/intscan.ini file provides an "HTTP
Scan" section, but it, too, is missing crucial port information.

Solution

The following workaround is for InterScan VirusWall 1.52, 1.53.

Introduction
InterScan VirusWall contains three vital proxy services: FTP, HTTP
and SMTP.  These proxy services act as a kind of "data filter" for
information and mail retrieved from the Internet before it gets to
your company's computers.  VirusWall is most effective when set up
between your company firewall or proxy server and your internal
network.
What is an HTTP Proxy?   It allows the Netscape Browser to reach
the Internet through another computer (usually a firewall) running
an HTTP Proxy Service.  HTTP Proxy Servers, such as the Netscape
Proxy Server, runs on a specific port (the default port being 8080
and not port 80) and transparently passes your requests to the
Internet servers outside of your private or public network.
Generally, once a proxy server is configured, as a user, you will
be unaware that it is acting as a relay for all your internet traffic.          VirusWall's HTTP proxy also binds to port 8080 by default and must
be reconfigured if 8080 is already in use by another process.  This
is discussed below.
Configuration

1. Edit the /etc/iscan/intscan.ini file and make the following changes:

a. Find the line within the intscan.ini file that begins with
   "HOrg=", under the section entitled "[HTTP-Scan]", and
   make the following modifications:
HOrg=<proxy_host_name> <port_id>

where <proxy_host_name> is the fully qualified host name of the proxy server, for example, host1.yourdomain.com and <port_id> is the assigned port number for the proxy server (usually 8080).

b. Under the section entitled "[HTTP-Scan]", add the following line directly beneath the "HOrg=" line:

port=<n>
where <n> is the port you want VirusWall to bind to and
listen.  If a proxy server is currently running on port
8080, then specify another unused port.

c. SCO highly recommends that "Level=" option be set to "ScanExt" as follows:

Level=ScanExt

The default is to "ScanAll", literally scanning every file on a given URL: images, text files, scripts, links, frames, etc. It could take many minutes before even the simplest page is finally displayed. The "ScanExt" option will cause VirusWall to use only common "DOS" extentions. (Please refer to the on-line InterScan VirusWall User Guide for more information on scanning by file name extentions).

2. Next bring up your Netscape browser (must be 3.0 or greater) and click on Options Tab -> Network Preferences -> Proxies Tab -> select Manual Proxy Configuration -> then select View. This will bring up the browser's Proxy Configuration form for your computer.

a. Fill in the following information to the"HTTP Proxy:" field:

<viruswall_proxy_host_name>
where this is the fully qualified name of host where VirusWall
is installed.  (Note: VirusWall can be installed on the same
host as the proxy server or on a different host.)
b. and "Port" field:
<port_id>

where this is the assigned port on the host where VirusWall is is installed.

c. Close each of the forms by clicking on the OK button.

d. Then select Options -> Save Options.

3. Finally, the httpd daemon for VirusWall has to be stopped and
   restarted.  Issue the following command from the UNIX prompt to
   get the process ID (pid) of httpd:
ps -ef|grep /etc/iscan/httpd

Then, issue the following commands from the UNIX prompt:

kill <pid>
/etc/iscan/httpd

From the Xinuos technical article database, record 105777. Reproduced with permission. The original is at www.sco.com/ta/105777, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.