SafeNet Sentinel, Руководство разработчика

Страница: 176 / 282

Chapter 7 – Implementing Secure Licensing
158 Sentinel Hardware Keys Developer’s Guide
should you terminate your application without allowing the users to
first save their work).
■
Allow the application to appear as if it is functioning properly, while in
fact it is not. (Be very careful if you use this method; less drastic
actions should be considered first.)
■ Display a critical error message and tell the user to contact your
technical support department.
These are just some suggested actions; you can implement any combination
of them to suit your needs. Remember, other events, such as network trans-
mission errors can also cause your application to detect a hardware key
problem. Since these are almost always innocent events, you should design
your strategy to be as forgiving of them as possible, while still maintaining
protection integrity.
Change your Strategy
Finally, as you perform software updates to your application in the field,
devote time to change and improve your security checks. The longer the
checks exist in the field, the more time there is to attack the mechanism.
Eventually, even the toughest checks might be overcome. However, if you
continually update your checks, then you can stay one step ahead. Consider
this action part of a planned maintenance to keep your security at its peak
level.
Note: For more personalized assistance in integrating the security checks in your
application, please contact our Technical Support using the information
given on page xv.