Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Chapter 6 – Secure Remote Updates
Contents Glossary Index Troubleshooting
164 Sentinel Hardware Keys Developer’s Guide
Because the Secure Update Wizard is integrated with the CodeCover/APIprotected
application at the license designing stage, its interface can be customized
to include your product and company-specific information (like,
product name, version, and copyright), text (like, e-mail address and content)
and images (like, splash image and application icon).
Question 3 - What are the steps that a customer undergoes to activate
the application using Secure Update Wizard?
The topic “Walk-through of Secure Update Wizard (Screens)” in the Sentinel
Keys Toolkit Help describes these steps.
Question 4 - Apart from the Sentinel Key and my application, what
other files I need to ship along with my protected application?
Please refer to Chapter 10, “Redistributables for Customers and Distributors,”
on page 223 for complete information.
Question 5 - Can I use the same request code (.req) file to generate
an update code (.upw) file, and a license addition (.nlf) file?
No, you are not advised to do so, because when the request code is generated,
the value of device update counter is stored in the *.req file. which is
incremented every time you follow any of the following operations on the
token:
Formatting before adding new licenses using *.nlf file.
Updating cheat counter value.
Updating Last known date and time (LKDT) value, once the lease
operation has been performed.
Updating user limit value.
Now, consider a scenario wherein you applied the *.req file to generate a
*.upw file, and later used the same *.req file to generate the *.nlf file. The
device update counter value in the *.req file may not match its value on the
token if you have performed any of the operations listed above, hence
restricting the process of applying the license addition code (*.nlf) file.