<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.vitcompany.com/en/history/Firmware_protection_key_in_OS_Linux?feed=atom</id>
	<title>Firmware protection key in OS Linux - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://docs.vitcompany.com/en/history/Firmware_protection_key_in_OS_Linux?feed=atom"/>
	<link rel="alternate" type="text/html" href="https://docs.vitcompany.com/en/history/Firmware_protection_key_in_OS_Linux"/>
	<updated>2026-04-04T13:10:32Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.35.1</generator>
	<entry>
		<id>https://docs.vitcompany.com/index.php?title=Firmware_protection_key_in_OS_Linux&amp;diff=595&amp;oldid=prev</id>
		<title>Sysop@vitcompany.com: 1 revision</title>
		<link rel="alternate" type="text/html" href="https://docs.vitcompany.com/index.php?title=Firmware_protection_key_in_OS_Linux&amp;diff=595&amp;oldid=prev"/>
		<updated>2015-03-10T11:22:37Z</updated>

		<summary type="html">&lt;p&gt;1 revision&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;==Introduction==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
# Configure HAPS Daemon on a GNU/Linux computer.&lt;br /&gt;
# Receive .c2v files necessary for .v2c key-file generation by the VIT representative.&lt;br /&gt;
# Install keys on a computer by means of HASP web interface.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==1. HASP Daemon Installation==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
:::::::::::::::::::::: Table 1.&lt;br /&gt;
{|  class=&amp;quot;wikitable&amp;quot; align=&amp;quot;center&amp;quot;; style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Linux distributions !! Driver location in the archive&lt;br /&gt;
|-&lt;br /&gt;
| Debian,Ubuntu ||  deb/aksusbd_2.1-1_i386.deb&lt;br /&gt;
|-&lt;br /&gt;
| RHEL,CentOS  ||  rpm/aksusbd-2.1-1.i386.rpm&lt;br /&gt;
|-&lt;br /&gt;
|  Slackware|| tgz/aksusbd-2.1.1-i386.tar.gz&lt;br /&gt;
|-&lt;br /&gt;
| ARCH Linux || the aksusbd 2.1-1 package is added to the repository by default.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
The latest version of the driver may be downloaded on the manufacturer’s website:&lt;br /&gt;
http://sentinelcustomer.safenet-inc.com/sentineldownloads/?s=&amp;amp;c=End+User&amp;amp;p=Sentinel+HASP&amp;amp;o=Linux&amp;amp;t=Runtime+%26+Device+Driver&amp;amp;l=all&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
::::::::::::::::::::::::::::::::: Table 2.&lt;br /&gt;
{|  class=&amp;quot;wikitable&amp;quot; align=&amp;quot;center&amp;quot;; style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Linux distributions !! Compatibility packages&lt;br /&gt;
|-&lt;br /&gt;
| Debian,Ubuntu ||  &lt;br /&gt;
 apt-get install ia32-libs&lt;br /&gt;
 dpkg -i --force-architecture deb/aksusbd_2.1-1_i386.deb&lt;br /&gt;
|-&lt;br /&gt;
| RHEL,CentOS  || &lt;br /&gt;
 yum install compat-libstdc++-296.i686 compat-libstdc++-33.i686&lt;br /&gt;
 rpm -i aksusbd-2.1-1.i386.rpm&lt;br /&gt;
|-&lt;br /&gt;
|  Slackware|| Manual installation of compat32 multilib. Example http://connie.slackware.com/~alien/multilib/&lt;br /&gt;
 tar xvzf tgz/aksusbd-2.1.1-i386.tar.gz&lt;br /&gt;
 cd aksusbd-2.1.1-i386&lt;br /&gt;
 sh dinst&lt;br /&gt;
&lt;br /&gt;
The packages install three Daemons: &amp;quot;aksusbd&amp;quot;, &amp;quot;hasplmd&amp;quot; and &amp;quot;winehasp&amp;quot;. Damones are launched and stopped by means of distribution package.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== 2. HASP Daemon Settings==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Here’s an example of a command that calls it out:&lt;br /&gt;
 curl -d &amp;quot;config&lt;br /&gt;
 accremote=1&lt;br /&gt;
 /config&amp;quot; http://localhost:1947/_int_/action.html&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Please note that the command has a couple of line start symbols. This is the way it should be written.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
==3. Receiving of .c2v files==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Libhasp directories should be installed to the system paths (that contain most of other libraries).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
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''.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[en: Firmware protection key in OS Linux|Firmware protection key in OS Linux]]&lt;br /&gt;
[[ru: Прошивка ключа защиты в ОС Linux|Прошивка ключа защиты в ОС Linux]]&lt;br /&gt;
[[es: Instalación de claves del programa|Instalación de claves del programa]]&lt;br /&gt;
&lt;br /&gt;
[[Category: Software]]&lt;br /&gt;
[[Category: Licensing]]&lt;/div&gt;</summary>
		<author><name>Sysop@vitcompany.com</name></author>
	</entry>
</feed>