        	AVIRA Desktop for Unix v 1.1.3 [Linux]

              Copyright (c) 2004-2005 by AVIRA GmbH

                    http://www.avira.com

        Document last updated on: June 20, 2005      


Thank you for using AVIRA Desktop for Unix v 1.1.3. This document
contains important information and we strongly advise you to read
the entire document and the related documentation available for
this product.

Contents:
- Description
- Features
- System Requirements
- Install
- Configuration
- Update
- Uninstall
- Registration
- Known Issues
- Feedback & Technical Support
- Copyright 


* Description

AVIRA Desktop for Unix v 1.1.3 [Linux] is an anti-virus perfect 
solution for Linux personal systems, which is able to completely
identify unwanted software and to isolate or repair the infected files.
AVIRA Desktop for Unix v 1.1.3 [Linux] is comprised of a resident 
(on-access) scanner, the Automatic Internet Updater, and a command line
scanner. The resident scanner is referred to as AVIRA Guard or AiGuard
(for short).


* Features

- Intuitive configuration;
- Command line scanner (on-demand);
- Optional user-friendly graphic interface "Graphic Interface TKAVIRA";
- Resident guard (on-access);
- Automatic removal of viruses or unwanted programs;
- Adware/Spyware Detection Support, in addition to the detection of 
  jokes, dialers and many forms of malware. This option has been 
  implemented in the antivirus engine for both on-access and  
  on-demand scan processes. Moreover, the AVIRA detection technology
  also recognizes Security Privacy Risk applications (SPR), Unusual
  Runtime Compression Tools and Double Extension Files;
- Heuristic detection for both macro and Win32 viruses;
- Recognition of all common archive types with configurable recursion
  level;
- Easy integration in automatic jobs, as scheduled scanning;
- Automatic Internet Updates;
- Extensive logging, warning and notification functions;
- Self Integrity Program Check;
- Excellent integration with Dazuko kernel module.


* System Requirements

For a working installation, you should consider these minimum
requirements:

- Platform: i386
- Operating System: Linux with 2.2 Kernel and GLIBC 2.2 or better
- 8MB free harddisk space for product installation
- 10MB free harddisk space for the working directory
- 32MB free memory space (64 MB recommended)

In order to use AiGuard you will need Dazuko. The Dazuko Project is a 
free software project that is developing a kernel module to provide 
3rd-party file access control. At the moment Dazuko only works for 
Linux kernels. 

Dazuko currently supports all 2.2.x - 2.6.x Linux kernels. You will 
need to compile Dazuko yourself in order to make use of AiGuard.
Information on how to do this can be found at the Dazuko Project 
website: http://dazuko.org/howto-install.shtml
 
============
 Disclaimer
============

AVIRA Desktop for Unix v 1.1.3 utilizes Dazuko (http://dazuko.org),
a free software project that provides a simple interface for 3rd-party
file access control. Dazuko is used as the basis for AiGuard, the
on-access scanner available with AVIRA Desktop for Unix v 1.1.3 [Linux]
package. AVIRA GmbH will take no responsibility for ANY problems
related to Dazuko itself. By building and/or installing Dazuko in order
to utilize AiGuard's on-access features, you are choosing to do so at
your own risk.

* Install

Login as root, change to the directory containing AVIRA Desktop for
Unix install files and run the install script.

./install

The script will do the following:
- copies the files to /usr/lib/AVIRA
- copies the configuration files to /etc
- creates a link in /usr/bin (if desired)
- creates links in rc.d directory (if desired)
- runs a configuration script (if desired)

In order to install AiGuard, you first need to compile the Dazuko 
module. Information on how to do this can be found in src/HOWTO-Dazuko 
file.

* Configuration

You can tune AVIRA for optimal performance, by using one of two
configuration methods: Configuration Files or Configuration Scripts.

Configuration Files
- avira.conf defines the automatic software update and the protocol
  for virus and unwanted programs detection.
- aiguard.conf defines the behavior of AVIRA Guard.

1. If you prefer to manually configure AVIRA for Unix instead of using
the provided configuration scripts, it is very simple.
First, you must restart AVIRA Updater manually in order to make the
settings effective:

/usr/lib/AVIRA/aiupdater restart

- /etc/avira.conf
  This file contains all the general flags and options that affect all
  AVIRA features.
  You should edit this file to suit your needs. Important directives
  to change would be:

  EmailTo - specifies where email notifications are sent (your server 
            must be configured as a mail server if you want to use
            external email addresses)

  LogTo   - specifies a file for logging data

  There are also additional directives for proxy support. If your
  machine is behind an HTTP proxy, you will need to set these options.

- /etc/aiguard.conf
  This file contains all the flags and options specific to AiGuard. You
  should edit this file to suit your needs. Important directives to
  change would be:

  AccessMask  - specifies what events cause a scan

  IncludePath - specifies a path for AiGuard to watch (all
                sub-directories are also watched)

  ExcludePath - specifies a path under the included paths that AiGuard
                should ignore (all sub-directories are also ignored)

If you change any of the configuration files, AVIRA program must be 
restarted:

/usr/lib/AVIRA/aiupdater restart
/usr/lib/AVIRA/aiguard restart


2. You can comfortably setup AVIRA using a configuration script. The
script intercepts the possible errors and restarts the necessary
processes.

AVIRA has two configuration scripts:
- configavira edits the settings in avira.conf
- configaiguard edits the settings in aiguard.conf and then in
  avira.conf, in order to make them work with AVIRA Guard.

Using the script is very easy. If you want to perform AVIRA general
configuration:
/usr/lib/AVIRA/configavira

If you want to perform AVIRA Guard configuration:
/usr/lib/AVIRA/configaiguard

The script reads the current setting values from avira.conf or
aiguard.conf, then it asks you to enter new values (if desired).
Possible values will be displayed.

For all parameters available in configuration files, please refer to 
product documentation.

* Update

If you are updating AVIRA software from a previous installation, simply
run the install script:
./install

The install script will identify a previous installation and 
automatically update necessary components.

Internet updates are done using HTTP. If your machine is running behind
an HTTP proxy server, you can configure AVIRA to use proxy (and other
updater options) by running:

     /usr/lib/AVIRA/configavira

or manually editing /etc/avira.conf file. Updates can be handled in two
different ways:

1) Automatic Internet Updater
   During installation you had the option of installing Automatic
   Internet Updater. This is a very simple daemon that runs in the 
   background. It sleeps until a certain time, it calls 
   'avira --update' and then it goes back to sleep. This program was
   designed for people who do not want to worry about configuring
   scripts or cron jobs for updates.
   You can manually start, stop, and see the status of the update     
   daemon with:

   /usr/lib/AVIRA/aiupdater start
   /usr/lib/AVIRA/aiupdater stop
   /usr/lib/AVIRA/aiupdater status

2) Manual Updates (or cron jobs)
   Another way of doing updates is manually, using 'avira --update'. 
   This command will give you visual feedback, so you can see what the
   update is doing. However, you can also automate it by putting the
   command in a cron job or within a script.
   
   A typical cron job entry (in /etc/crontab) would look like this:

   45 6 * * * root /usr/lib/AVIRA/avira --update -q

   This would cause AVIRA to check for updates every day at 6:45 
   (the -q means it runs in quiet mode, without any output). You
   could also write your own scripts, which look at the exit code to
   know if an update was successful. Here is a simple script to
   demonstrate this:

------------------ BEGIN SCRIPT -------------------
#!/bin/sh

/usr/lib/AVIRA/avira --update -q
case $? in
  0)
    echo "AVIRA is up-to-date"
    ;;
  1)
    echo "AVIRA has updated itself"
    ;;
  *)
    echo "AVIRA had an error trying to update"
    ;;
esac
------------------- END SCRIPT --------------------

   If the updater is run as root, then it will do more than simply
   download updated software.
   It will also safely and securely reload any AiGuard, or AVIRA 
   MailGate processes.

   Note: When running --update as root, it is best to give the full
   path for the command. For example, you should call:

             /usr/lib/AVIRA/avira --update

         and NOT:

             avira --update

   If you do not include the full path, you may get a warning
   from AVIRA that it could not determine the true path.

   If you do not want the process to always run as root, you could use
   --check option as a regular user (to check for updates):

   /usr/lib/AVIRA/avira --check --update
   
   If an update is available, you could log in as root and manually run
   the updater:

   /usr/lib/AVIRA/avira --update

   Whenever AVIRA makes an update, it logs this information using
   syslog. If you have specified a custom log file, it is also logged
   into this file. Furthermore, if you have specified email 
   notifications, it will send an email message each time an update was
   successful or if there was an error (email messages are not sent if
   an update was not needed).

* Uninstall

The uninstall script will remove the previously installed files.

Login as root, change to the directory containing AVIRA Desktop for
Unix install files and run the uninstall script.

./uninstall desktop

The script will do the following:

- remove the installed files from the /usr/lib/AVIRA
- remove the symbolic links in /usr/bin (if found)
- remove the init scripts links in the rc.d directory

Note: If more than one AVIRA product is found installed on the system,
the uninstall script will not remove AVIRA core files (AVIRA Command
Line Scanner and VDF files) or the Internet Updater.

* Registration

After purchasing the product from AVIRA Sales or from one of the 
nearest AVIRA Partners, along with the proof of purchase you will 
receive the Registration Code (RC), which is required to obtain the
Activation Key (AK). AK is needed for the product to run with Update
Service.

You can obtain the Activation Key only after registering with the RC at
http://register.avira.com within 30 days from the RC delivery date.

Activation Keys (AK) can be placed in any directory but we recommend 
you to put them in the /etc directory together with the AVIRA
configuration files. Make sure that the key file has proper 
permissions. You need to specify the path to the AK on the License line
in your /etc/avira.conf file, for example:

   License YOUR-REGISTRATION-CODE /etc/your-activation-key


* Known Issues

- AiGuard uses a kernel module (Dazuko) to allow on-access scanning. 
  Dazuko must be compiled for the specific kernel that is running on 
  the system. Be aware that if you perform a system upgrade, you may
  also have a new kernel. This means that the Dazuko module must be
  re-compiled for this new kernel. Otherwise AiGuard will no longer 
  function after the system upgrade.

- If you are running AiMailGate and AiGuard, it is critical that 
  AiGuard does NOT watch AiMailGate's SpoolDir and TemporaryDir. If
  AiGuard watches the SpoolDir, then it will block access to all
  concerning files that AiMailGate temporarily unpacks from
  attachments. AiMailGate will then be unable to scan the attachments
  and allow the mail to pass through. You can solve this problem by
  setting your AiMailGate SpoolDir and TemporaryDir to a directory that
  is NOT watched by AiGuard.

- It is possible that AiGuard can hang your system during shutdown. 
  This occurs if AiGuard is watching system directories AND you do
  not properly shutdown AiGuard using the aiguard script. When shutting
  down, Linux usually issues a SIG_STOP to all processes. This will
  freeze all the AiGuard daemons, thus not permitting them to do
  scanning. However, the kernel module (Dazuko) is not aware that the
  daemons are stopped and it will wait forever (hang) until a daemon 
  becomes available. In short, always use the aiguardscript to properly
  shutdown AiGuard before doing a system shutdown. This is a problem
  with Dazuko that will hopefully be resolved soon.

  NOTE: The installation program will ask if you want AiGuard to run 
  automatically at startup. If you choose "yes", then you should not
  have to worry about this problem.

- Using multiple kernel modules that intercept file system calls can be
  very dangerous. It is highly recommended that AiGuard is NOT used in
  conjunction with other kernel modules which intercept filesystem 
  calls.

- In some cases AVIRA Guard does not properly restart after a
  successfull update.


* Copyright

Copyright (c) 2004-2005 AVIRA GmbH. All rights reserved. No part of 
this material can be reproduced, in any way, by any means. The product
and the documentation coming with the product are protected by AVIRA 
GmbH's copyright.
AVIRA GmbH reserves the right to revise and modify its products 
according to its own necessities. AVIRA GmbH cannot be held responsible
for any special, collateral or accidental damages, related in any way
to the use of this document.

* Feedback & Technical Support

Technical support is available at: support@avira.com.
Please do not hesitate to contact us if you discover any problems or if
you have any suggestions.

For commercial related issues please write to sales@avira.com.
AVIRA Website: http://www.avira.com