Hasp SRM - v.4.0 Release Notes: Software Rights Management
Hasp SRM - v.4.0 Release Notes: Software Rights Management
A l a d d i n . c o m
Table of Contents
Supported Platforms
To ensure that you have the most comprehensive and up-to-date list of supported platforms check the
www.Aladdin.com/SRMplatformSpt page.
General Information
HASP SRM Vendor Keys
When you purchase HASP SRM, you are provided with two HASP SRM Vendor keys—the
HASP SRM Master key and the HASP SRM Developer key.
The HASP SRM Developer key is used by your software engineers in conjunction with the
HASP SRM protection tools to protect your software and data files.
The HASP SRM Master key is used in conjunction with HASP SRM Business Studio and is attached
to the Business Studio Server. It is used by your production staff to create licenses and lock them to
HASP SRM protection keys, to write specific data to the memory of a HASP SRM protection key,
and to update licenses already deployed in the field.
Every Business Studio Server machine must have a HASP SRM Master key connected. If you have
installed the Activation components on a separate server to that on which the Management
components are installed, you must ensure that each instance of the Activation server has a
HASP SRM Master key connected that contains your Aladdin licenses.
Known Issues
The known issues from HASP SRM v.4.0 that are likely to have the most significant impact on users
are listed below, according to component.
Ref #11416: In certain instances, a protected Mach-O binary may have a different owner and
permissions than it had prior to protection with HASP SRM Envelope. This is caused because
HASP SRM Envelope designates the current user (that is, the user applying the protection) as the
owner of the newly-created files.
Ref #10925: When launching HASP SRM Envelope (GUI) from a command line prompt, you
must use the -p switch and specify a project file.
Ref #11578: If a HASP SRM Master key is disconnected during the protection process, the
message “+(void)load” may be displayed.
Ref #10691: To protect applications that read from their code section, the Protection against
memory dump option may need to be disabled. However, consider the balance between the
advantages of enabling “protection against memory dump” against the disadvantages of not
invoking this option.
Ref #10929: You cannot run protected PPC binaries on Intel Mac x64 and Intel 10.4.11 operating
systems.
Contact Details
For assistance, or to report problems, contact your local Aladdin representative, or create a support
call here.