| |
_Frequently
Ask Questions
| You get an excellent level of protection regarding
both hardware and the libraries that interact
with the application. Every transaction is carried
out while encrypted between the protector and
the routines. At the same time the libraries and
the protected executable are wrapped around with
encryption routines along with anti-debug codes
and software traps to prevent violation. At the
core of the protection system is a technology
that encrypts the software by means of a hardware
key, which makes it virtually impossible for a
hacker to access the protection routines. |
| Yes, the software protector does not interfere
with the normal use of these devices. |
| Yes, by means of the automatic protection environment
it is possible to protect a program and declare
that associated files be handled with encryption.
Once the application is protected, this data may
only be accessed from the application with the
embedded encrypted on-line HARDkey routines. |
| HARDkey NET keys (orange casing) may be shared
for varying applications to be accessed from different
points on a network . Our protection system does
not impose any restriction on the developer ,
who may opt for implementing a setup with or without
license control for the end user. If you decide
to carry out license control, we can offer you
the tools for limiting the number of simultaneous
users that may access the keys . There are other
key models which are designed specially for single
user applications (HARDkey STD, SuperPro 797 y
SuperPro USB). |
| Yes , there are no restrictions in this sense.
You may opt for either of the two setups. The
drivers and utilities needed in each case are
provided in the KIT. |
| Communication between the service which manages
access to the key and the protected application
is carried out by means of Windows "MailSlot"
technology which ensures the link through any
protocol using the network. This is a great advantage
as its functioning is not limited to a particular
protocol but the system works with whatever protocol
configured (NetBios, IPX, TCP/IP, etc). |
|
|
