Firmware protection key in OS Linux

From VIT company
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Introduction

The following User Guide describes the installation process of HASP software key produced by Safenet Company for GNU/Linux OS. Upon reading this guide user should be able to:

  1. Configure HAPS Daemon on a GNU/Linux computer.
  2. Receive .c2v files necessary for .v2c key-file generation by the VIT representative.
  3. Install keys on a computer by means of HASP web interface.


1. HASP Daemon Installation

The SDK archive of HASP catalog contains the protection key driver ver. 2.1.1. The exact location in the archive is mentioned in table 1.

Table 1.
Linux distributions Driver location in the archive
Debian,Ubuntu deb/aksusbd_2.1-1_i386.deb
RHEL,CentOS rpm/aksusbd-2.1-1.i386.rpm
Slackware tgz/aksusbd-2.1.1-i386.tar.gz
ARCH Linux the aksusbd 2.1-1 package is added to the repository by default.


The latest version of the driver may be downloaded on the manufacturer’s website: http://sentinelcustomer.safenet-inc.com/sentineldownloads/?s=&c=End+User&p=Sentinel+HASP&o=Linux&t=Runtime+%26+Device+Driver&l=all The driver is distributed in 32-bit version only. The use of 32-bit compatibility packages is necessary to install it on a 64-bit OS, packages names and means of installation are mentioned in table 2:

Table 2.
Linux distributions Compatibility packages
Debian,Ubuntu
apt-get install ia32-libs
dpkg -i --force-architecture deb/aksusbd_2.1-1_i386.deb
RHEL,CentOS
yum install compat-libstdc++-296.i686 compat-libstdc++-33.i686
rpm -i aksusbd-2.1-1.i386.rpm
Slackware Manual installation of compat32 multilib. Example http://connie.slackware.com/~alien/multilib/
tar xvzf tgz/aksusbd-2.1.1-i386.tar.gz
cd aksusbd-2.1.1-i386
sh dinst

The packages install three Daemons: "aksusbd", "hasplmd" and "winehasp". Damones are launched and stopped by means of distribution package.


2. HASP Daemon Settings

This entry will be of special interest for people with no graphic interface installed on their computers. By default, the HASP Daemon web-console is accessed by localhost only which requires a JavaScript-compatible browser and that is not possible in text mode. However, the remote access may be allowed by a simple POST request. Curl utility may be used in such case.


Here’s an example of a command that calls it out:

curl -d "config
accremote=1
/config" http://localhost:1947/_int_/action.html


Please note that the command has a couple of line start symbols. This is the way it should be written.


To make sure all settings are applied, a remote connection to a port 1947 should be established from a computer with a browser using IP-address of a computer that has HASP Runtime installed.


3. Receiving of .c2v files

Manufacturer’s libraries should be installed to generate .c2v files. They may be found in an archive at haspvlib directory. They should be copied to a /var/hasplm/directory, automatically created when HASP Daemon was installed.


Libhasp directories should be installed to the system paths (that contain most of other libraries).


In order to generate .c2v files, respective empty keys (EOAWT or AAOTB) should be installed. They may be found in the empty_keys archive. To install the key, just go to the Update/Attach section of HASP Daemon’s interface and specify the empty key file. After that user is ready to generate .c2v file. Launch the .c2v generator for your kind of file from the hasprus directory: hasprus_XXXXX i c2vname.c2v.


The resulting file is to be transferred to your VIT Company manager that later will provide user with a key update which should be installed the same way as an empty key. Have a quick and easy configurating.

Firmware protection key in OS Linux Прошивка ключа защиты в ОС Linux Instalación de claves del programa