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

Chapter 2 – Sentinel Hardware Keys SDK Components
Contents Glossary Index Troubleshooting
36 Sentinel Hardware Keys Developer’s Guide
the Sentinel Key attached to the system. This tool also provides the developer
an option to customize the source files and the destination path, using
the CodeCover option XML file.
You need to attach both the Developer Key and Sentinel Key (of the same
developer ID), to protect files and program keys using the Command-Line
CodeCover Utility. However, if you are using the Custom CodeCover Key,
the Developer Key and Sentinel Key are not required as in that case the utility
can be used for applying only the CodeCover protection and not for
programming Sentinel Keys.
For more information, refer to “CodeCover Protection Using the Command-
Line Utility” on page 91.
Key Programming APIs
Key Programming APIs include the API functions used for:
Programming the Sentinel Hardware Keys
Provides a Toolkit independent programming environment wherein
the license group files are exported by the developer and programmed
into the memory of the Sentinel Keys using the Key Programming
API functions.
Refer to section, “Programming Sentinel Keys using the Key
Programming APIs” on page 208.
Creating Update Packets: The update packets are generated to:
Enable creation of data buffers 1 (also termed as update packets)
that overwrites new values to the existing features in the Sentinel
Hardware Keys in field, or
Overwrite the values (provided at the license designing stage) by
key programming the Sentinel Key, with .ISV/.DIS/.OPR file,
before it is distributed to the end user.
Note: SFNTCreateUpdatePacket API function of the Key Programming library is
1.Set of encrypted data.