BitDefender for Linux File Server

Short Install & Upgrade Guide BitDefender for Linux File Server

  1. PACKAGE NAMING

BitDefender for Linux Samba File Servers package is named considering the following parameters:

BitDefender-samba-{version}.{os}.{arch}.{pkgtype}.run {version} is the package version. For example, 1.6.2-1 is version 1, subversion 6.2, package build 1. Note that package build may be missing.

{os} is Linux for the moment, *BSD and other Unices will be available soon. Linux has 2 versions, one compiled with gcc 2.9x and the other with gcc 3.x. Choose the appropriate version for your system.

{arch} is the processor type. i586 is the current development version.  It will work on Intel Pentium II, Pentium III, Pentium IV, AMD alternatives and other compatible processors.

{pkgtype} refers to the package management tool we use in order to install the files on your computer. This is one of rpm, deb or tar: rpm uses the Red Hat Package Manager deb uses dpkg tar is the most portable method. Please note that, however, the tar packages do not contain
source code. Please install the appropriate package for your system.


2. INSTALL

NOTE: Before installing BitDefender for Linux File Servers, you should check if your Samba package have built-in VFS and ACL support. At the release date, there is full support for Samba from version 2.2.7a up to 3.0.12 and further versions will be supported as they appear. If you
have another version of Samba and there is no precompiled BitDefender VFS module, you have to get the source from /opt/BitDefender/src directory and compile it by yourself. For more about this, please see the install notes from the above mentioned directory.

If there is no installed Samba meeting these conditions, you should
follow these steps:
- backup your current Samba configuration (mostly located in /etc/samba
  directory), and stop smbd.
- uninstall your current Samba package (the procedure may vary regarding
  your Linux distribution and package management).
- if you will not find precompiled Samba packages with built-in VFS and
  ACL support, you must download the source code, compile it and
  install.

You may use the following procedure:
- install attr-devel, acl-devel packages from your Linux distribution
  CD-ROM set
- download Samba source code package, for example:
  $ wget http://us4.samba.org/samba/ftp/old-versions/samba-2.2.7a.tar.gz
  $ tar zxf samba-2.2.7a.tar.gz && cd samba-2.2.7a/source
  $ ./configure --prefix=/usr/local --with-smbmount --with-syslog
    --with-acl-support
  $ make
  $ su -
  # make install
- restore your samba configuration back in /etc/samba (optionally, you
  may run testparm to check your smb.conf file. If testparm does not
  find smb.conf file, you must create a symlink in /usr/local/lib to the
  actual /etc/samba/smb.conf file).


Before you begin the installation process, we recommend you to check that the installation kit is not corrupted (this can happened sometimes, if you downloaded it). Please run the following command:

# sh ./BitDefender-samba-{version}.{os}.{arch}.{pkgtype}.run --check

The answer should be:

Verifying archive integrity... MD5 checksums are OK. All good.

If you get a different answer, please re-download the installation kit.

All packages, regardless of the {pkgtype}, are installed using:

# sh ./BitDefender-samba-{version}.{os}.{arch}.{pkgtype}.run

For example, this should be run in the directory where the package is
located:

# sh ./BitDefender-samba-1.6.2-1.linux-gcc3.i586.rpm.run

This will unpack the BitDefender packages, and will launch the install
script, that will in turn install the BitDefender components. These are:
- BitDefender-engines
- BitDefender-core
- BitDefender-samba

Please follow exactly the instructions during the installation process.

For additional options for the installer, please run:

# sh ./BitDefender-samba-{version}.{os}.{arch}.{pkgtype}.run --help

Due to the internal Samba architecture, the file generally named bdvfs.so can integrate with only one version of Samba, the one which it was built for. Therefore the full file name respects the following rule: bdvfs-{samba_version}.so, where {samba_version} represents the version
of Samba the module was built for, such as 3.0.10. If the package does not contain the VFS module you need for your Samba server, please use the sources from /opt/BitDefender/src to compile a compatible module.

After the installation you will get an up and running file server virus scanner. To complete the configuration and protect the shares, you have to add a line to /etc/samba/smb.conf file in the desired [share] section or, eventually, in the [global] section to protect some or all of the
shares.

For Samba version 2.x, the module may be installed no matter where and this line should contain the full path to it, such as (please pay attention to the version numbers, as mentioned before):

vfs object = /opt/BitDefender/lib/bdvfs-2.x.x.so

For Samba version 3.x, the module should be symlinked into Samba VFS directory. Regarding Samba installation, the location of VFS directory may vary. Depending on your setup, usual locations might be: /usr/lib/samba/vfs or /usr/local/samba/lib/vfs. The symlink MUST have
the name bdvfs3.so. To create it, use the following command, replacing the paths and version according to your configuration:

# ln -sf /opt/BitDefender/lib/vfs/bdvfs-3.0.x.so
                    /usr/lib/samba/vfs/bdvfs3.so

The line added to /etc/samba/smb.conf should contain only the file name,
without the so extension, such as:

vfs object = bdvfs3

You may insert this line in the [share] sections you want to protect.  Alternatively, you might protect all the shares by inserting the above line in the [global] section.

Finally, start smbd daemon (for example run smbd -D as root).


3. UNINSTALL

If you run the installation kit with the --uninstall parameter, the package will try to uninstall a previous version. Please note that the tar version actually wipes the installation directory, so make sure you backup any data you need.

For example:

# sh ./BitDefender-samba-{version}.{os}.{arch}.{pkgtype}.run --uninstall


4. UPGRADE FROM PREVIOUS BITDEFENDER VERSIONS

If you already have BitDefender v1.5.6 or v1.6.x on your system the installation kit is able to automatically upgrade keeping your current settings. In order to upgrade just hit "enter" or type "yes" when you are asked if you want to upgrade.

If you have a BitDefender version older than 1.5.6 automatic update is not supported so you need to uninstall the previous version first. 
Please follow these steps:

a) Stop BitDefender services. Run:
  # /etc/init.d/bd stop

b) Uninstall the old BitDefender.
  - run: sh ./BitDefender. --uninstall
  - delete /tmp/BDNP, if it exists. Run: rm -fr /tmp/BDNP

If you installed from the .tar version, delete the installation folder (by default this is /opt/BitDefender). Then remove the BitDefender
integration from your File Server.

c) Install the new version, following the instructions from the INSTALL
(2) section.