© 9/2004 Aladdin Knowledge Systems, Ltd. All rights reserved.

Aladdin and HASP are registered trademarks of Aladdin Knowledge Systems, Ltd. All other company and product names are trademarks or registered trademarks of their respective owners.
Aladdin is the #1 vendor in the Software Licensing
Authentication Tokens market for 2002 and 2003.
IDC Bulletin #31432, 2004

Software Protection and Licensing Guide

Software Protection
and Licensing
Guide

For more info: e A l a d d i n . c o m / H A S P

North America T: 1-800-562-2543, 1-847-818-3800, F: 1-847-818-3810, Email: [Link]@[Link]
International T: +972-3-636-2222, F: +972-3-537-5796, Email: HASP@[Link]
UK T: +44-1753-622266, F: +44-1753-622262, Email: [Link]@[Link]
Germany T: +49-89-89-42-21-0, F: +49-89-89-42-21-40, Email: [Link]@[Link]
Printed in Israel
05772

Benelux T: +31-30-688-0800, F: +31-30-688-0700, Email: [Link]@[Link]

France T: +33-1-41-37-70-30, F: +33-1-41-37-70-39, Email: [Link]@[Link]
Spain T: +34-91-375-99-00, F: +34-91-754-26-71, Email: [Link]@[Link]
Israel T: +972-3-636-2222, F: +972-3-537-5796, Email: [Link]@[Link]
Asia Pacific T: +852-2166-8605, F: +852-2166-8999, Email: [Link]@[Link]
Japan T: +81-426-60-7191, F: +81-426-60-7194, Email: [Link]@[Link]
COPYRIGHTS AND TRADEMARKS
The HASP®HL system and its documentation are copyrighted (C) 1985 to present by
Aladdin Knowledge Systems Ltd. All rights reserved.
HASP and Hardlock are registered trademarks of Aladdin Knowledge Systems Ltd.

HASP®HL Basic, HASP®HL Pro, HASP®HL Max, HASP®HL Time and HASP®HL
Net are trademarks of Aladdin Knowledge Systems Ltd.
All other trademarks, brands, and product names used in this guide are trademarks of
their respective owners.

i
3 Sub-licensing
After merging the Software in your computer program(s) according to section 2 above,
you may sub-license, pursuant to the terms of this Agreement, the merged Software
and resell the hardware components of the Product which you purchased from Aladdin,
to distributors and/or users. Preceding such a sale and sub-licensing, you shall
incorporate by reference in your contracts with such distributors and/or users, and
otherwise provide for all distributors and/or users to be bound by, the warranties,
disclaimers, and license terms specified by Aladdin in this Agreement.

4 Prohibited Users
Except as specifically permitted in Sections 1,2 and 3 above, you agree not to (i) use,
modify, merge or sub-license the Software or any other of Aladdin's products except as
expressly authorized in this Agreement and in the HASP HL Protection and Licensing
Guide; and (ii) sell, license (or sub-license), lease, assign, transfer, pledge, or share
your rights under this License with/to anyone else; and (iii) modify, disassemble,
decompile, reverse engineer, revise or enhance the Software or attempt to discover the
Software's source code; and (iv) place the Software onto a server so that it is accessible
via a public network; and (v) use any back-up or archival copies of the Software (or
allow someone else to use such copies) for any purpose other than to replace an
original copy if it is destroyed or becomes defective. If you are a member of the
European Union, this Agreement does not affect your rights under any legislation
implementing the EC Council Directive on the Legal Protection of Computer
Programs. If you seek any information within the meaning of that Directive you should
initially approach Aladdin.

5 Limited Warranty
Aladdin warrants, for your benefit alone, that (i) the Software, when and as delivered
to you, and for a period of three (3) months after the date of delivery to you, will
perform in substantial compliance with the HASP HL Protection and Licensing Guide,
provided that it is used on the computer hardware and with the operating system for
which it was designed; and (ii) that the HASP(r) key and the HASP(r) HL key for a
period of twelve (12) months after the date of delivery to you, will be substantially free
from significant defects in materials and workmanship.

iv
6 Warranty Disclaimer
ALADDIN DOES NOT WARRANT THAT ANY OF ITS PRODUCT(S) WILL
MEET YOUR REQUIRMENTS OR THAT ITS OPERATION WILL BE
UNINTERRUPTED OR ERROR-FREE. TO THE EXTENT ALLOWED BY LAW,
ALADDIN EXPRESSLY DISCLAIMS ALL EXPRESS WARRANTIES NOT
STATED HERE AND ALL IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. NO ALADDIN'S DEALER,
DISTRIBUTOR, RESELLER, AGENT OR EMPLOYEE IS AUTHORIZED TO
MAKE ANY MODIFICATIONS, EXTENSIONS, OR ADDITIONS TO THIS
WARRANTY. If any modifications are made to the Software or to any other part of the
Product by you during the warranty period; if the media and the Product is subjected to
accident, abuse, or improper use; or if you violate any of the terms of this Agreement,
then the warranty in Section 5 above, shall immediately be terminated. The warranty
shall not apply if the Software is used on or in conjunction with hardware or program
other than the unmodified version of hardware and program with which the Software
was designed to be used as described in the HASP HL Protection and Licensing Guide.

7 Limitation of Remedies
In the event of a breach of the warranty set forth above, Aladdin's sole obligation shall
be, at Aladdin's sole discretion: (i) to replace or repair the Product, or component
thereof, that does not meet the foregoing limited warranty, free of charge; (ii) to refund
the price paid by you for the Product, or component thereof. Any replacement or
repaired component will be warranted for the remainder of the original warranty period
or 30 days, whichever is longer. Warranty claims must be made in writing during the
warranty period and within seven (7) days of the observation of the defect
accompanied by evidence satisfactory to Aladdin. All Products should be returned to
the distributor from which they were purchased (if not purchased directly from
Aladdin) and shall be shipped by the returning party with freight and insurance paid.
The Product or component thereof must be returned with a copy of your receipt.

v
8 Exclusion Of Consequential Damages
The parties acknowledge, that the Product is inherently complex and may not be
completely free of errors. ALADDIN SHALL NOT BE LIABLE (WHETHER
UNDER CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE) TO
YOU, OR ANY THIRD PARTY (INCLUDING, WITHOUT LIMITATION, YOUR
DISTRIBUTORS AND USERS OF YOUR SOFTWARE PROGRAM) FOR ANY
LOSS OR DAMAGE (INCLUDING INDIRECT, SPECIAL OR CONSEQUENTIAL
DAMAGES), INCLUDING, WITHOUT LIMITATION, ANY LOSS OR DAMAGE
TO BUSINESS EARNINGS, LOST PROFITS OR GOODWILL AND LOST OR
DAMAGED DATA OR DOCUMENTATION, SUFFERED BY ANY PERSON,
ARISING FROM AND/OR RELATED WITH AND/OR CONNECTED TO ANY
USE OF THE SOFTWARE AND/OR ANY COMPONENT OF THE PRODUCT,
EVEN IF ALADDIN IS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

9 Limitation Of Liability
IN NO EVENT SHALL ALADDIN'S TOTAL MONETARY OBLIGATION AND
LIABILITY, UNDER ANY CLAIM FOR ANY CAUSES OF ACTION PURSUANT
TO THIS AGREEMENT, EXCEED THE PAYMENTS MADE BY YOU TO
ALADDIN FOR THE PRODUCT/S THAT GAVE RISE TO THE ACTION OR
CLAIM, AND IF NO SUCH PRODUCT/S ARE SO APPLICABLE THEN
ALADDIN'S LIABILITY SHALL NOT EXCEED THE AMOUNT OF FEES PAID
BY YOU TO ALADDIN HEREUNDER DURING THE TWELVE (12) MONTHS
PRECEDING THE EVENT.

10 No Other Warranties
Except as specifically provided herein, Aladdin makes no warranty or representation,
either express or implied, with respect to its products as described in the preamble of
this agreement, including its quality, performance, merchantability or fitness for a
particular purpose.

vi
11 Termination
Your failure to comply with the terms of this Agreement shall terminate your license
and this Agreement. Upon termination of this Agreement by Aladdin: (i) the license
granted to you in this Agreement shall expire and you, upon termination, shall
discontinue all further use (including without limitation sub-licensing) of the Software
and other licensed Product(s); and (ii) you shall promptly return to Aladdin all tangible
property representing Aladdin's intellectual property rights and all copies thereof and/
or shall erase/delete any such information held by it in electronic form. Sections 1, 4,
6, 7, 8, 9, 10, 11 and 12 shall survive any termination of this Agreement.

12 Governing Law & Jurisdiction

This Agreement shall be construed and governed in accordance with the laws of Israel
(except for conflict of law provisions) and only the competent courts of Tel-Aviv,
Israel shall have jurisdiction in any conflict or dispute arising out of this Agreement.
The application of the United Nations Convention of Contracts for the International
Sale of Goods is expressly excluded. The failure of either party to enforce any rights
granted hereunder or to take action against the other party in the event of any breach
hereunder shall not be deemed a waiver by that party as to subsequent enforcement of
rights or subsequent actions in the event of future breaches.

13 Third Party Software

If the Product contains any software provided by third parties, such third party's
software is provided “As Is” without any warranty of any kind and shall be subject to
any and all limitations and conditions required by such third parties.

14 Miscellaneous
This Agreement represents the complete agreement concerning the license hereunder
and the subject matter hereof and may be amended only by a written agreement
executed by both parties. If any provision of this Agreement is held to be
unenforceable, such provision shall be reformed only to the extent necessary to make it
enforceable.
I HAVE READ AND UNDERSTOOD THIS AGREEMENT AND AGREE
TO BE BOUND BY ALL OF THE TERMS.

vii
 Certifications

CE Compliance
The HASP product line complies with the CE EMC Directive and
related standards*. HASP products are marked with the CE logo and
a HASP CE conformity card is included in every shipment or upon
demand.

*EMC directive 89/336/EEC and related standards EN 55022, EN

50082-1.

FCC Compliance
FCC authorities have determined that HASP is not a Class B Computing Device
Peripheral and therefore does not require FCC regulation.

UL Certification
The HASP product line successfully completed UL 94 Tests for Flammability of
Plastic Materials for Parts in Devices and Appliances. HASP products comply with UL
1950 Safety of Information Technology Equipment regulations.

ISO 9001:2000 Certification

The HASP product line is designed and manufactured by
Aladdin Knowledge Systems, Inc., an ISO 9001:2000
certified company. Aladdin's quality assurance system is
approved by the International Organization for
Standardization (ISO), ensuring that Aladdin products and
customer service standards consistently meet specifications in
order to provide outstanding customer satisfaction.

viii
Certificate of Compliance
Upon request, Aladdin Knowledge Systems, Inc. will supply a Certificate of
Compliance to any software developer who wishes to demonstrate that the HASP
product line conforms to the specifications stated. Software developers can distribute
this certificate to the end user along with their programs.

ix
 Chapter 12
HASP License Manager

This chapter describes the HASP License Manager. It includes

the following topics:
• HASP License Manager for Windows/Mac/Linux
• Configuring the HASP License Manager
• Configuring applications protected with HASP HL Net
• Adjusting the HASP HL Net environment

Overview of HASP License Manager

The HASP License Manager maintains a login table which lists
all the protected applications that have logged into a deployed
HASP HL Net. The table identifies each protected application,
and the station that activated the application. An application and
its station are listed in the login table until the application logs
out from the HASP HL Net.
The HASP License Manager uses the login table to keep track
of simultaneous usage of a protected application within a
networking environment. It ensures that the number of stations
accessing the protected feature or application does not exceed
the maximum number specified in the license for the feature as
licensed by the software vendor. By default, the login table can
track up to 250 applications.

HASP HL Software Protection and Licensing Guide 151

HASP License Manager

HASP License Manager for Windows

The HASP License Manager for Windows is available as:
• An application for Windows 2000/XP/
Server 2003
• A service for Windows 2000/XP/Server 2003
The HASP License Manager for Windows can communicate
through the TCP/IP and IPX protocols. The protocols can be
loaded and unloaded using the HASP License Manager
graphical user interface or settings in the [Link] configuration
file.

The NetBIOS protocol is only available for

applications protected with the HASP4 system.

Distributing the HASP License Manager for Windows

If you have protected your software to work with HASP HL Net
keys, you should distribute the HASP License Manager to your
end users. It is recommended that you also distribute Aladdin
Monitor. For more information, refer to "Aladdin Monitor"
(page 181).
There are two ways to distribute the HASP License Manager.
• You can distribute the setup file — [Link] — separately
to your customers. See the next section for specific
installation instructions. This file is available in your HASP
HL installation CD under the following directory:
Windows/Installed/Redistribute/LM/
• You can use the HASP License Manager Installation API to
include the HASP License Manager service as part of your
application’s installation program. This custom API is
documented in separately on the HASP License Manager
help file.

152 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

Installing HASP License Manager under Windows

Both types of HASP License Managers can be installed with the
setup file [Link].
Install the HASP License Manager on the station to which the
HASP HL Net key is connected.
The installation can be customized using the following methods:
• Use the configuration file [Link], see "HASP License
Manager Configuration Settings" (page 163).
• Use the License Manager Installation API (only Win32
service), see "Settings for the IPX Protocol (Win32 only)"
(page 166).

On a Windows 2000/XP/ 2003 Station

The HASP License Manager for Windows
2000/XP/2003 is [Link]. Use the setup file [Link] to
install it.
1. Install the HASP HL device driver and connect the HASP
HL Net key to a station.
2. Install the HASP License Manager by running [Link]
from your HASP HL installation CD and follow the
instructions of the installation wizard. As installation type,
select Service.

HASP HL Software Protection and Licensing Guide 153

HASP License Manager

You can also integrate the HASP License Manager

service installation into your application by using
samples for the HASP License Manager Install API,
which can be found in the following directory:
Windows/Installed/Samples/LM Install.

Activating and Deactivating HASP License Manager

HASP License Manager Application
To activate the HASP License Manager, select the application
from the Start menu or Windows Explorer. The HASP License
Manager application is always active when any protocol is
loaded and a HASP HL Net is connected.
To deactivate the application, select Exit from the main menu.

HASP License Manager Service

To activate and deactivate the HASP License Manager service,
use the Windows Service administration in the Control Panel.
You can also use Aladdin Monitor to start and stop the HASP
License Manager service.

Operating the HASP License Manager

You can operate the HASP License Manager using the graphical
user interface.
To open the main window of the graphical user interface,
double-click the application’s icon in the system tray.

154 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

Figure 12.1 HASP License Manager GUI

The HASP License Manager main window displays the

following information:
• HASP License Manager version number
• Status of each protocol (loaded, unloaded, or failed to load)
and the date and time of the last change of status
• Status of the HASP License Manager (active or not active)
You can close the HASP License Manager main window by
clicking the close button at the right corner of the title bar. The
HASP License Manager continues running, and the icon
remains in the system tray.
To exit the program, choose Exit from the menu bar.

If the HASP License Manager is installed as a

Windows NT service, you cannot exit using this
menu option.

Loading Protocols
To enable a protocol, select it from the Load menu. You can
only enable protocols which have been installed on the
computer.

HASP HL Software Protection and Licensing Guide 155

HASP License Manager

Unloading Protocols
To disable a protocol, select it from the Remove menu.

Viewing the Activity Log

To view a log of the HASP License Manager activities, select
Activity Log from the menu bar. The Activity Log window is
opened.
To view the log for a specific protocol, select the protocol from
the drop-down list.

Multiple Network Adapters

The HASP License Manager binds itself to the default Windows
network adapter that is usually the first available network
adapter.
To allow the HASP License Manager to serve requests arriving
at other network adapters on a multi-homed system, IP
Forwarding must be enabled within the Windows networking
configuration.
When using the HASP License Manager on
Windows operating systems, please note that the
default network adapter can vary from one
Windows version to another.

156 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

HASP License Manager for Mac

The HASP License Manager for Mac is available for Mac OS X.
It can communicate through the TCP/IP protocols.
The HASP License Manager for Mac consists of a daemon and
a graphical user interface. The HASP License Manager for Mac
can be operated by using the graphical user interface. You can
also operate the daemon from the command line.

Distributing the HASP License Manager for Mac

The following directory on the HASP HL installation CD
contains all software required for distributing HASP License
Manager to your end users:
MacOS/Installed/Redistribute/LM/
There are four methods for distributing the HASP License
Manager:
• An installation image which can easily be downloaded by
your end users from your FTP site.
• An installation package that can be included as part of a
multi-package installation.
• Source files that can be integrated to a single package
installation.
• Scripts sent to end users with instruction on how to install the
daemon through a command-line shell.
All four methods are included in folders within the directory
specified above. Each folder contains a [Link] file
containing detailed information on usage and installation
procedures.

HASP HL Software Protection and Licensing Guide 157

HASP License Manager

Activating and Deactivating HASP License Manager

To activate the HASP License Manager, start the application
from the applications menu and start the daemon by choosing
Start Daemon in the application window. Alternatively you can
start the daemon using the installation script.

To load the HASP License Manager automatically,

activate the Activate in system startup option.

Operating HASP License Manager

You can operate the HASP License Manager using the graphical
user interface. You can also operate it from the command-line
tool, see "Switches for the HASP License Manager" (page 162).
The HASP License Manager for Mac displays the following
information:
• Server name and IP address of the server
• Available switches
• If the daemon is activated during system start up
• The daemon status
The following options are available:
• Setting switches (only when the daemon process is not
running)
• Starting and stopping the daemon
• Activating the daemon at start up

158 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

Setting a Server Name

You can assign up to six server names to the HASP License
Manager.
To assign a server name:
1. Stop the daemon if it has already been started.
2. Activate the SRVNAMES option.
3. Enter up to six names — separate the names with semicolons,
colons, or spaces.
The names are assigned once the daemon is started.

Avoid using non-ASCII characters for server

names, since their codes differ form system to
system. Server names are not case-sensitive. You
cannot assign server names to a running daemon.

Setting a Configuration File

You can configure the HASP License Manager for Mac using a
configuration file. To set name and path of the configuration
file, activate the CFGFILE option and enter the path and name.
For information about the configuration file, refer to "HASP
License Manager Configuration Settings" (page 163).

Starting and Stopping the Daemon

To start and stop the daemon, use the buttons in the application
window.

Activating the Daemon Automatically

The daemon can be automatically activated at system startup. To
do this, enable the Activate in system startup option.

HASP HL Software Protection and Licensing Guide 159

HASP License Manager

HASP License Manager for Linux

The HASP License Manager (LM) for Linux is available for all
distributions of Linux. RPM packages are however,
only available for the following Linux distributions:
• Red Hat 8 and Red Hat 9
• SuSE 8.x and SuSE 9.x.
The HASP HL LM for Linux consists of a daemon.
The HASP License Manager for Linux was not
available as this manual went to print. Please
consult your local HASP representative for
information on release dates and other updates.

Distributing the HASP License Manager for Linux

The following directory on the HASP HL installation CD
contains all software required for distributing HASP License
Manager to your end users:
Linux/Installed/Redistribute/LM/
There are two methods for distributing the LM.
• RPM packages, see the next section for installation
instructions.
• Scripts sent to end users with instruction on how to install the
daemon through a command-line shell.
All two options are included in folders within the directory
specified above. Each folder contains a [Link] file
containing detailed information on usage.

Installing HASP License Manager

You can automatically install the HASP HL LM for Linux using
RPM packages for the distributions listed above.

160 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

To install HASP HL LM on SuSE 8.x or 9.x

Use the following SuSE RPM package:
• rpm -i HASP [Link]

To install HASP HL LM on RedHat 8 or 9

Use the following Red Hat RPM package:
• rpm -i HASP [Link]

To install HASP HL LM on other Linux Distribution

You must manually install the HASP License Manager.
1. Unpack the archive using:
tar-xzf [path/]linuxlm_8_30.[Link]
The ‘linux-HASP HLlm_8_30’ directory is created.
2. Change to this directory and execute as root:
./dinst
This command installs the HASP License Manager and
configures the system to automatically start the daemon at
system boot.

Activating and Deactivating the HASP License Manager

If properly installed, the HASP License Manager should
automatically be activated once the system is rebooted.
To deactivate the HASP License Manager, you must uninstall
the daemon. For example, to uninstall the HASP License
Manager running on Red Hat 7.3 enter the following:
rpm -e HASP HLlm-redhat

HASP HL Software Protection and Licensing Guide 161

HASP License Manager

Customizing the HASP License Manager

When installing and operating the HASP License Manager you
may want to adapt it to a particular network environment. You
can use one the following methods:
• Operate the HASP License Manager with switches.
• Use the configuration file [Link].
• Use the License Manager Installation API (Win32 only).

Switches for the HASP License Manager

The HASP License Manager can be activated with various
switches. These commands instruct the HASP HL system on
which protocols to use, and how to serve the HASP HL Net
clients.
Table 12.1 HASP License Manager Switches

Windows
Linux

Mac
Switch Explanation

-c Specifies the location of the configuration file for yes no yes

the HASP License Manager.
-help Displays a list of available switches. yes no yes

162 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

HASP License Manager Configuration Settings

To configure the HASP License Manager, use the [Link]
configuration file. A configurable sample of [Link] is
included in the Redistribute folder on your HASP HL
installation.

Search Order
You can place [Link] and the executable of the HASP License
Manager in the same directory or in any other location
according to the [Link] search order described in Table 12.2.
Table 12.2 Search Order for [Link]

Operating System Search Order

Windows 2000/XP/ Executable file directory
Server 2003 Current directory
Windows 32-bit system directory
Windows 16-bit system directory
Windows directory
Path
Linux To use a configuration file, you
must set the name and the path for
the configuration file using the -c
switch.
Mac To use a configuration file, you
must set the name and the path for
the configuration file using the -c
switch.

HASP HL Software Protection and Licensing Guide 163

HASP License Manager

Server settings
Server parameters are specified in the [Link] and not in
the command line. This way, parameter specification for the
License Manager service is easier, and configuration is
simplified and consolidated within a single file.
For Win32 platforms, the [Link]. should reside in the
directory from which the program executable is deployed. For
Linux and Mac platforms there is no default storage location for
the file; you must specify which configuration file to use. For
example:
./HASP HLlm -c /etc/[Link]

[Link]. Settings
Boolean switches may have the following values:
Table 12.3 Boolean Values for HASP HL LM [Link]

1 yes true enabled

0 no false disabled

Global LM Settings
You can fine tune settings for the HASP License Manager
through its configuration file, [Link]. The HASP License
Manager configuration file includes the [NHS_SERVER]
section which is used to set global LM settings. The following is
a list of keywords in the [NHS_SERVER] section:

Keyword NHS_USERLIST

Description Maximum number of concurrent logins to LM. Maximum

number is 65520.

Default 250

Example NHS_USERLIST =1000

164 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

Keyword NHS_SERVERNAMES

Description Server name to match the name a client requests. Maximum of 6

names. Maximum 7 characters per name. Multiple names
separated by commas.

Default none

Example NHS_SERVERNAMES= cad, 3242e3

Keyword NHS_HIGHPRIORITY

Description Runs LM at high priority. Default runs the LM at normal

priority. Switch applies only to Win32. When this switch is set
to yes, check to see how performance of other services (file
server, web server, etc.) running on the same machine are
affected.

Default no – runs at normal priority.

Example NHS_HIGHPRIORITY= no

Settings for the IP Protocol

You can fine tune settings for the HASP License Manager
through the configuration file, [Link]. This file includes the
[NHS_IP] section which is used to define settings for the IP
protocol. The following is a list of keywords in the [NHS_IP]
section:

Keyword NHS_USE_UDP

Description Setting can be either enabled or disabled.

Default enabled

Example NHS_USE_UDP=enabled

HASP HL Software Protection and Licensing Guide 165

HASP License Manager

Keyword NHS_IP_PORTNUM

Description IP port number. This switch applies only to Win32. Port number
475 is the exclusively registered IANA number for Aladdin LM.

Default 475

Example NHS_IP_PORTNUM=475

Clients must use the same port!

Keyword NHS_IP_LIMIT

Description Specifies the range stations which are allowed to access the
currently activated HASP HL LM. The last byte may be a range.
Multiple entries should be separated by commas. The list may
be split through several lines. The following wildcard (asterisk)
byte combinations are possible: 4th,4th,3rd or 4th,3rd,2nd. An
additional bitmask can be specified as the number of single bits
(e.g. [Link]/8).

Default none

Example NHS_IP_LIMIT = 10.242.18-99,[Link]/16,

[Link]/24,192.0.0*,194.0*,*,11.*,*,
*[Link]-12/30,[Link]

Settings for the IPX Protocol (Win32 only)

You can fine tune settings for the HASP License Manager
through the configuration file, [Link]. The file includes the
[NHS_IPX] section which is used to define settings for the IPX
protocol. The following is a list of keywords in the [NHS_IPX]
section:

Keyword NHS_USE_IPX

Description Setting can be either enabled or disabled.

166 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

Default enabled

Example NHS_USE_IPX= yes

Keyword

Keyword NHS_ADDRPATH

Description Path to HASP [Link] file. The IPX address of the current
LM is written to HASP [Link] in the specified directory.
Clients can specify this file in their [Link] file.

Default current directory

Example NHS_ADDRPATH=c:\temp

Keyword NHS_APPENDADDR

Description Appends address data to the [Link]. If enabled, the current

LM’s address is added to an existing HASP [Link]. This is
particularly useful when multiple HASP License Managers
exist. All the LMs can be searched by the client. The LM does
not search for duplicates when adding an address.

Default replace

Example NHS_APPENDADDR=no

HASP HL Software Protection and Licensing Guide 167

HASP License Manager

Keyword NHS_USESAP

Description Setting can be enabled or disabled to allow the HASP HL LM to

announce itself to the network through the Service Advertising
Protocol (SAP). SAP enables clients to find the LM for different
subnets. IPX is normally configured to run a virtual subnet on
Win 2000/XP/Server 2003 machines, so SAP is essential in
enabling clients to find the LM.

Default enabled

Example NHS_USESAP=enabled

Keyword NHS_IPX_SOCKETNUM

Description The IPX socket number. All clients must use the same default
socket number. The number should not be altered. Note: clients
must use the same port!

Default 0x7483

Example NHS_IPX_SOCKETNUM= 0x7483

Settings for the NetBIOS Protocol

You can fine tune settings for the HASP License Manager
through the configuration file, [Link]. The file includes the
the [NHS_NETBIOS] section which is used to define settings
for the NetBIOS protocol. The following is a list of keywords in
the [NHS_NETBIOS] section:

Keyword NHS_USE_NETBIOS

Description Setting can be enabled or disabled. If you are certain that you do
not need NetBIOS for LM communication, disable the switch to
save network and memory resources.

Default enabled

Example NHS_USE_NETBIOS=enabled

168 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

Keyword NHS_NBNAME

Description Use switch to alter name. Note: Clients must use the same name
which must be unused in your NetBIOS name space. Names
must follow NetBIOS naming conventions.

Do not use this switch unless you are certain that

you need to specify a new NetBIOS name.

Default enabled

Example NHS_NBNAME=MyNBName

Keyword NHS_USE_LUNA_NUMS

Description Only included so as to be compatible with older versions.

Default all (automatic)

Example NHS_USE_LUNA_NUMS=3,0,7,2

Configuring HASP HL Net Clients

This section describes how an application protected for HASP
HL Net — the HASP HL Net client — can be configured
through a configuration file.
When the client finds the relevant configuration file, it reads and
uses the information contained in the file. If not, default values
are used.
In the HASP HL Net client configuration file you can fine tune
how the client searches for the HASP License Manager.

HASP HL Software Protection and Licensing Guide 169

HASP License Manager

The default filename of the HASP HL Net configuration file is

[Link]. A copy of [Link] is included in the directory
containing the HASP License Manager. If you change the name
of the configuration file, you must implement the new name
when protecting the application with HASP HL Envelope or the
HASP HL API.

Search Sequence for Configuration File

The search sequence for the file depends on the operating
system and the type of application.
The protected application searches for the configuration file
after the first login call. For more information refer to "The
HASP HL API Login Function" (page 61). The application
undertakes the following search sequence.
Table 12.4 [Link] Configuration File Search Order

Operating System Search Sequence

Win32 Executable file directory →
Current directory →
Windows system directory →
Windows directory →
Path
Mac OS X Current directory
(Carbon)
Mac OS X Current directory →
Home directory of the current user →
/etc. directory

Under Mac OS X, [Link] is searched without a

leading period. If you are using a case-sensitive
system on Mac OS X, make sure that the filename
[Link] is in lowercase.

170 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

Sections in the Configuration File

The HASP HL Net client configuration file consists of three
optional sections:
• [NH_COMMON] for general settings
• [NH_IPX] for the IPX protocol
• [NH_TCPIP] for the TCP/IP protocol
The [NH_COMMON] section contains global settings for all
configuration file sections. The other two sections contain
settings which fine tune operations for the specific protocol.

Specifying Keywords
In each section, you can specify either general or section-
specific keywords. If you set a general keyword in one of the
three protocol sections, you override the setting in the
[NH_COMMON] section (for that protocol only).
Use the section-specific keywords to adjust additional settings
for a particular protocol.
API and Envelope settings override configuration file settings.
Every line of the HASP configuration file you receive with the
HASP HL software is preceded by a semicolon (;). To use a line,
remove the semicolon. If you want to add comments, precede
them with a semicolon.

Names of the HASP HL Net configuration files and

their keywords are not case-sensitive — exception
being names under Mac OS X when a case-
sensitive file system is used.

The following sections describe each section in the HASP HL

Net client configuration file. For each keyword, the possible
values and a short description are included. Default values are
listed when applicable.

HASP HL Software Protection and Licensing Guide 171

HASP License Manager

[NH_COMMON]

Section specific for [NH_COMMON]

Keyword nh_ipx

Description Enables the use of the IPX protocol.

Possible values enabled, disabled

Keyword nh_tcpip

Description Enables the use of the TCP/IP protocol.

Possible values enabled, disabled

General keywords for [NH_COMMON]

Keyword nh_session

Description Sets the maximum length of time during which the protected
application attempts to communicate with the HASP License
Manager.

Possible values numerical value

Default 2 seconds

Keyword nh_send_rcv

Description Sets the maximum length of time for the HASP License
Manager to either send or receive a package.

Possible values numerical value

Default 1 second

172 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

[NH_IPX]

Section specific keywords for [NH_IPX]

Keyword nh_use_bindery

Description Enables the IPX protocol to work with Novell’s BINDERY.

Possible values enabled,disabled

Default disabled

Keyword nh_use_broadcast

Description Enables the use of the IPX broadcast mechanism.

Possible values enabled, disabled

Default enabled

Keyword nh_bc_socket_num

Description Sets the socket number for the broadcast mechanism.

The number is hexadecimal.

Possible values hexadecimal value

Default 7483H

Keyword nh_use_int

Description 2F_NEW means that the IPX protocol only uses interrupt 2Fh.
7F_OLD means that the IPX protocol only uses the 7Ah
interrupt.

Possible values 2F_NEW, 7F_OLD

Default 2F_NEW

Keyword nh_server_name

HASP HL Software Protection and Licensing Guide 173

HASP License Manager

Description Communicates with the HASP License Manager under a

specified name.

Possible values <name1>,<name2>,...

Keyword nh_search_method

Description Determines if the protected application communicates with

HASP License Manager on a local network, or with any HASP
License Manager on the Internet.

Possible values localnet, internet

Default internet

Keyword nh_datfile_path

Description Specifies the location of the HASP License Manager address

file.

General keywords for [NH_IPX]

Keyword nh_session

Description Sets the maximum length of time during which the protected
application tries to communicate with the HASP License
Manager.

Possible values numerical value

Default 2 seconds

Keyword nh_send_rcv

Description Sets the maximum length of time for the HASP License
Manager to either send or receive a package.

Possible values numerical value

Default 1 second

174 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

[NH_TCPIP]

Section-specific keywords for [NH_TCPIP]

Keyword nh_server_addr

Description Sets IP addresses for all the searchable HASP License

Managers. Unlimited number of addresses and multiple lines are
possible.

Possible values <address1>,<address2>

Examples IP address: [Link]

Local hostname: [Link]

Keyword nh_server_name

Description Communicates with the HASP License Manager under a

specified name. Each name can contain up to 7 characters and
you can specify up to 6 names.

Possible values <name1>,<name2>

Keyword nh_use_broadcast

Description Enables the use of the UDP broadcast mechanism.

Possible values enabled, disabled

Default enabled

General Keywords for [NH_TCPIP]

Keyword nh_session

Description Sets the maximum length of time during which the protected
application tries to communicate with the HASP License
Manager.

Possible values numerical value

Default 2 seconds

HASP HL Software Protection and Licensing Guide 175

HASP License Manager

Keyword nh_send_rcv

Description Sets the maximum length of time for the HASP License
Manager to either send or receive a package.

Possible values numerical value

Default 1 second

Adjusting the HASP HL Net Environment

This section describes additional HASP License Manager
settings and [Link] keywords to accommodate the
deployment of a HASP HL Net within a specific network
environment.

Defining the Range of Stations under IPX

With IPX, you can allow specific stations on a different segment
to access the HASP License Manager.

To allow access from a different segment:

1. Load the HASP License Manager with the -ipxnosap switch.
This ensures that the address of the HASP License Manager is
not advertised using the SAP mechanism, and is advertised in
the HASP HL Net [Link] address file.
2. Edit the [Link] file as follows:
• In the [NH_COMMON] section, set NH_IPX =
Enabled
• In the [NH_IPX] section, set NH_USE_BROADCAST =
Disabled
• In the [NH_IPX] section, set NH_USE_BINDERY =
Disabled

176 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

These settings instruct the protected application running on

stations in the range to search for the address file and read the
address of the HASP License Manager.
3. Copy the protected application and the [Link] file to the
same directory.

Defining the Range of Stations under TCP/IP

There are two ways of defining the range of stations under
TCP/IP. You can either specify the range of stations that the
HASP License Manager serves, or you can specify that the
range of stations search for a particular HASP License Manager.

Specifying the Range Using [Link]

The HASP License Managers for Windows, Win32 and Mac can
read a [Link] configuration file. You can edit this file to
specify the range of stations the HASP License Manager serves
under TCP/IP.

To specify the range of stations

Edit the [Link] file as follows:
• In the [NHS_SERVER] section, NHS_IP_LIMIT =
<ipaddr> [,<ipaddr....]

Sample Formats for <ipaddr>

When you specify the range of stations using [Link], you can
use any of the following formats:
• [Link]
The HASP License Manager serves only the station with the
specified IP address.
• 10.1.2.*
The HASP License Manager serves only stations that match the
specified IP address mask, i.e. [Link] through [Link].
• 10.1.*.*

HASP HL Software Protection and Licensing Guide 177

HASP License Manager

The HASP License Manager serves only stations that match the
specified IP address mask, i.e. [Link] through [Link].

Limiting station access to the HASP HL Net in a TCP/

IP-based network:
1. Edit [Link] and set the range of stations.
2. Copy [Link] to a location accessible by the HASP License
Manager.

Specifying the range using [Link]

You can edit the HASP HL Net configuration file to specify that
the HASP License Manager (according to address) should
search a range of stations.

Specifying a range of stations

1. Edit the [Link] file: In the [NH_TCPIP] section, set
NH_SERVER_ADDRESS= <address of HASP License
Manager>
2. Copy the [Link] to a location accessible only to the
desired range of stations.

Adapting the Time-out Length

The HASP License Manager cannot serve more than one request
at a time. The time-out length determines how long a protected
application repeatedly tries to access the HASP License
Manager before giving up.
In almost all networks, the default time-out values are sufficient,
so you only need to change the default values in networks that
have a HASP HL Net connected to a slow or busy station.

Defining time-out length

In the appropriate section of the [Link] file, set:
NH_SESSION = <m>
NH_SEND_RCV = <n>

178 Aladdin Knowledge Systems Ltd © 2004.

Distributing HASP HL HASP License Manager

where m and n are measured in seconds. By default, m is 2

seconds and n is 1 second.

Defining the Number of Protected Applications Served

With the HASP License Manager, you can change the default
number of stations served. By default the HASP License
Manager can serve a maximum of 250 (Win32, Mac and Linux)
stations.
The HASP License Manager allocates memory space for the
maximum number of protected applications. If necessary, you
can save memory space by changing this default value.

Changing the default memory space allocation

Load the HASP License Manager with the switch:
nhsrvw32 -userlist = n
where n is the number of stations it serves.
The -userlist switch is only available for Win32.

HASP HL Software Protection and Licensing Guide 179

 © 9/2004 Aladdin Knowledge Systems, Ltd. All rights reserved. Aladdin and HASP are registered trademarks of Aladdin Knowledge Systems, Ltd. All other company and product names are trademarks or registered trademarks of their respective owners.
Aladdin is the #1 vendor in the Software Licensing
Authentication Tokens market for 2002 and 2003.
IDC Bulletin #31432, 2004

Software Protection and Licensing Guide

Software Protection
and Licensing
Guide

For more info: e A l a d d i n . c o m / H A S P

North America T: 1-800-562-2543, 1-847-818-3800, F: 1-847-818-3810, Email: [Link]@[Link]
International T: +972-3-636-2222, F: +972-3-537-5796, Email: HASP@[Link]
UK T: +44-1753-622266, F: +44-1753-622262, Email: [Link]@[Link]
Germany T: +49-89-89-42-21-0, F: +49-89-89-42-21-40, Email: [Link]@[Link]
Printed in Israel
05772

Benelux T: +31-30-688-0800, F: +31-30-688-0700, Email: [Link]@[Link]

France T: +33-1-41-37-70-30, F: +33-1-41-37-70-39, Email: [Link]@[Link]
Spain T: +34-91-375-99-00, F: +34-91-754-26-71, Email: [Link]@[Link]
Israel T: +972-3-636-2222, F: +972-3-537-5796, Email: [Link]@[Link]
Asia Pacific T: +852-2166-8605, F: +852-2166-8999, Email: [Link]@[Link]
Japan T: +81-426-60-7191, F: +81-426-60-7194, Email: [Link]@[Link]