Install AL Download Protection

al_logo1.gif (1351 bytes)  Thank you for selection of AL Download Protection!

Contents

About AL Download Protection

AL Download Protection is server-side counterpart of Anti-Leech Plugin.

AL Download Protection works like small personal Anti-Leech Online server, provide you with the following functions:

Together with Anti-Leech Plugin, this software provide an ultimate protection of your web content.

Before you install AL Download Protection

Before you start installation process, please, check the following items.

License Agreement

Please, read carefully license agreement for AL Download Protection.

Netscape 4.x users: There is no <iframe> support in the browser, press HERE to view license agreement.

If you do not accept this agreement, please, abort installation and remove AL Download Protection distributive from your computer.

If you accept the agreement, you may continue installation.

System requirements

AL Download Protection is written in Perl and require the following Perl interpreter:

AL Download Protection also require some Perl modules to be installed.
Installer will check a presence of required modules and assist you to install missing modules.

You can also try to install AL Download Protection with ActivePerl 5.8.x.x at your own risk.
Do not hesitate to consult support@anti-leech.com in such cases.

Installation

1. Prepare directories at hosting server
 

Done


You should create 3 directories at hosting server: private, public, and alinstall and provide appropriate access permissions on ones. You can rename public and private to any names which you like, however in this text below we will always refer to these directories as public and private. The alinstall directory is needed only for installation process and should be removed after.

There are different instructions for Unix hosting users and Windows hosting users.

Instructions
Unix users Windows users
  1. Create directory public (with any name which you like) outside a Document Root of your server or virtual host.
  2. Create directory private (with any name which you like) inside a Document Root of your server or virtual host.
  3. Create directory alinstall  inside a Document Root of your server or virtual host.
  4. Set permissions 'Full access for all' (chmod 777) to to these  three directories
  5. Check that web server is allowed to invoke executable files from public and alinstall directories. Note, on some systems  this is possible only inside cgi-bin directory and it's subdirectories. Contact your server administrator in case of problems
  1. Create directory public (with any name which you like) outside a Document Root of your server or virtual host.
  2. Create directory private (with any name which you like) inside a Document Root of your server or virtual host.
  3. Create directory alinstall  inside a Document Root of your server or virtual host.
  4. Consult your server administrator and check that web server have permissions to read and write to all three directories.
  5. Consult your server administrator and check that web server is allowed to execute execute Perl scripts (.pl) from public and alinstall directories. Note, on some systems  this is possible only inside cgi-bin directory and it's subdirectories
Details and Comments
AL Download Protection is to be located in two directories called public and private.
  • public: contains things that must be accessible from the web, including encrypted packages, management and statistics scripts
  • private: contains things that must not be accessible from the web, including packages in source form, database files and helper script libraries

Public and private are generalized names which are used to refer to the directories during installation process.
You can assign any appropriate names to these directories and locate the directories in any appropriate location at the hosting host.
However, be sure, that public directory is inside Document Root of your server/virtual host and private directory is outside the Document Root.

AL Download Protection scripts are invoked by web server as cgi scripts. Please, provide permissions for:
- read and write access to public and private directories for all users (777 at Unix)
- invocation of  perl scripts from the web in public directory

Note, that web server can invoke cgi scripts on behalf of a user other than you.
This depends on your server software and security policy of your server administrator.

Directory alinstall  is temporary directory which will be used during installation process.
Requirements to location of alinstall and permissions on it are similar to ones for public directory.

 

2. Decompress distributive
 

Done


You should transfer files from distributive archive (alinstall.tar.gz or alinstall.zip) into alinstall directory and adjust access permissions for transferred files.
Archives contain a directory hierarchy and you should keep the hierarchy unchanged when copying files.
Instructions
Unix users - without terminal access Windows users
  1. Decompress alinstall.zip archive at your personal workstation, use pkunzip, WinZip or similar program. You will see alinstall directory with subdirectories and files inside.
  2. Connect to web server with FTP client. Please, use one of advanced FTP clients, such as Far, WS_FTP or CuteFTP. Do not use command-line ftp program.
  3. Upload all content of alinstall directory from your workstation to alinstall directory at hosting server. Check that directory structure is not changed during copying.
  4. Change access mode of all *.pl files in alinstall directory at hosting server to 755, using your FTP client.
  5. Check that access mode of all subdirectories and contained files of alinstall permit reading for all at least, adjust the mode if necessary with a help of your FTP client. 
  1. Decompress alinstall.zip archive at your personal workstation, use pkunzip, WinZip or similar program. You will see alinstall directory with subdirectories and files inside.
  2. Connect to web server with FTP client. Please, use one of advanced FTP clients, such as Far, WS_FTP or CuteFTP. Do not use command-line ftp program.
  3. Upload all content of alinstall directory from your workstation to alinstall directory at hosting server. Check that directory structure is not changed during copying.
Unix users - with terminal access
  1. Upload archive alinstall.tar.gz on to hosting server, to the parent directory of alinstall directory (i.e. alinstall/..).
  2. At shell prompt, change current directory to this parent directory.
  3. Decompress the archive with tar utility. Type at shell prompt:

    tar -zxf alinstall.tar.gz
  4. Check that all *.pl files in alinstall directory have access mod 777. Type at shell prompt:

    ls -l alinstall/*.pl

    the mode of each file should be -rwxr-xr-x. If this not true, type at shell prompt:

    chmod 755 alinstall/*.pl

    to make mode correct.
  5. Check that access mode of all subdirectories and contained files of alinstall permit reading for all at least ('r' letter in last mode triad), adjust the mode if necessary, by typing at shell prompt:

    chmod -R a+r alinstall
Details and Comments

Archives alinstall.tar.gz and alinstall.zip both contain Installer scripts and files to install.
The first is prepared for decompressing at Unix machines and is not recommended for usage on Windows machines.
The second is prepared for decompressing on Windows machines.

It is important to preserve directory structure of alinstall when decompressing and copying files.

Installer will be invoked by web server as cgi script. To let it run, you must provide permissions for:
- read and write access to the directory alinstall itself for all users (must be done at Step 1)
- read access to it's subdirectories for all users (on Unix: 444 on at least; on Windows this is usually true without additional measures)
- execute programs in the directory for all users (Unix systems only; 777 at least for all .pl files)
- invoke Perl scripts (Windows) or cgi programs (Unix)  from the web.

Note, that web server can invoke cgi scripts on behalf of a user other than you.
This depends on your server software and security policy of your server administrator.

 

3. Switch to web interface
 

Done


You should connect to web server and open an URL which corresponds alinstall directory.
Instructions

Launch your browser and enter URL of alinstall directory. If everything is OK, you will see a copy of this page, which is included into distributive and now will be invoked from the hosting server.

 

4. Invoke Installer and set configuration of your AL Protection instance
 

Done


You should tell an Installer where at the hosting server you have created public and private directories and which URL should be used to access public directory from the web.
Instructions

Invoke the installer: install.pl.

It will prompt you for

  • system type (Unix/Windows; already set correctly)
  • locations of public and private directories
  • URL to access public directory from the web

Fill these fields and press 'Continue'.

If everything is OK, Installer will install AL Protection files to specified directories.

Otherwise, installer report problem(s). The problems usually connected with violation of conditions on access permissions at Steps 1-2. Please, correct problem(s) and invoke installer again.

 

Details and Comments

Installer will transfer necessary files to directories which we have created at Step 1.

On Unix systems it is important to set appropriate file access mode. Installer will do this automatically.

At this step installations of AL Protection itself is completed. However, it is needed to check a presence of required Perl modules at the server and setup your login and password, so continue with following steps.

 

5. Check the system for required Perl modules
 

Done


AL Protection require a number of Perl modules. Some of them are not installed by default with Perl interpreter.

Invoke the next part of Installer to check for a presence of these modules.

Instructions

Invoke checking part of the installer: check_perl.pl.

The script will test Perl instance and report a presence of required modules.

If all modules are present, skip Step 6 and go directly to Step 7.

Otherwise execute Step 6 and the repeate Step 5 again.

The check_perl.pl script output a list of missing modules. Use this list at Step 6.

 

 

6. Install missing modules
 

Done


You need to install missing Perl modules. Follow suggestions of check_perl.pl script and this text below.

There is a number of options how to install the modules. Selection of appropriate option depends on hosting server security policy and conditions of your hosting agreement. Please, select an option which is better for you from list below.

Instructions
Preferred way
Ask your provider or server administrator to install required modules (or do this by yourself if you have administrative privileges at the host). A list of modules to install is printed by check_perl.pl script at Step 5. Note that all required modules can be found in required-unix.tar.gz and required-ppm.zip archives. These archives contain CPAN and PPM packages respectively. You can download these archives from Anti-Leech site.
Less preferred way - stealth installation in your private directory
Unix users Windows users
Download required-unix.tar.gz and put it into alinstall directory at the hosting server. Then invoke module installer script: install_modules.pl. See comments on this script below.
If your attempt failed, please, do not hesitate to contact support@anti-leech.com.
After success, repeat Step 5.
Download libwin.zip archive and decompress it at your personal workstation, then copy lib\... tree from the archive into lib subfolder of the private directory on the hosting server. Please, use one of advanced FTP client (CuteFTP, WS_FTP, Far), don't use command line ftp program, it is too difficult. Important: an original structure of the tree must be preserved unchanged.
Warning: This will work with ActivePerl v.5.6.x.6xx only.
If your attempt failed or the hosting host is running other ActivePerl version, please, do not hesitate to contact support@anti-leech.com.
After success, repeat Step 5.
Details and Comments
The best way is to install necessary modules into Perl system libraries. All users of Perl will can use them and server's disk space will be used more efficiently. However, only server's administrator have sufficient privileges to install the modules there. So it is better to contact him and ask to install the modules.

If this is not possible, the only way is to install modules into your private directory.

The way is very different for Unix and Windows machines. This is because a set of preinstalled Perl modules is very different for Unix and Windows.
Besides this, modules for Unix are distributed in source code form, including C language sources.

The install_module.pl script builds required modules from sources.
The script prints result of preliminary analysis of the system and a summary of the work, which can detect does it complete its work or not.
After completion, please, repeat Step 5.
Output of the module also includes a lot of listings, which are not informative for final users.
However, these listings can help us to detect an error or unusual condition in case if something goes wrong.
Keep the listings in such cases.

 

7. Setup login and password
 

Done


You should setup login and password to let AL Download Protection authenticate you when you will access it for management purpose.
Instructions

Invoke setup script: new_account.pl, and specify login and password.
Details and Comments
It should not be allowed anyone to access your private AL Download Protection, so the software must be sure that you are you.
Login and password are used for this purpose.

You can setup your login and password with new_account.pl script only once. The second time (for instance, you upgrade the software) the script will not work. However, you can change the password in administrative form of AL Download Protection (you should log in first).

The script can not work until Digest::MD5 Perl module installed at the hosting server.

 

8. Test the instance
 

Done


To be sure that installation completes successfully, log in your AL Download Protection.
Instructions

In your browser, enter an URL corresponding to public directory of your installation.
Details and Comments
This must be the same URL that you entered at Step 3.
Installer (Step 3) lists the URL in its output.

If everything is OK, installation is completed. You can start work immediately.

 

8. Remove temporary directory
 

Done


The alinstall directory is no longer needed. Remove in completely with all its contents.
Instructions
Unix users - without terminal access Windows users
Remove directory alinstall with all subdirectories and contained files completely.

Use capabilities of your FTP client to remove a directory tree.

Please, use one of advanced FTP clients such as Far, WS_FTP or CuteFTP.
Do not use command-line ftp utility.

Remove directory alinstall with all subdirectories and contained files completely.

Use capabilities of your FTP client to remove a directory tree.

Please, use one of advanced FTP clients such as Far, WS_FTP or CuteFTP.
Do not use command-line ftp utility.

Unix users - with terminal access
  1. At shell prompt, change current directory  to the parent directory of alinstall directory (i.e. alinstall/..).
  2. Remove alinstall directory. Type at shell prompt:

    rm -rf alinstall
Details and Comments
The alinstall directory is no longer needed. Besides this:
-  it can contain a lot of temporary data
- on some systems can  have less restrictive access permissions to data than private and public directories.
These are the reasons to remove this directory.

 

 

Web resources for the installation


Copyright (C) 1999-2003 WakeNet AB. All right reserved.