02.04.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Remote Update Codes<br />

Contents Glossary Index Troubleshooting<br />

counter value in the Cheat Counter (only for non-RTC keys) field,<br />

and then clicks Generate. The loadable license packets are generated<br />

and exported in the form of *.nlf file.<br />

Note: The update packets for LKDT packet is also integrated with the *.nlf file.<br />

7. The developer sends the license addition (*.nlf) file using an e-mail to<br />

the customer.<br />

8. The customer applies the license addition code to use the new license.<br />

Remote Update Codes<br />

Request Code<br />

Refers to the code generated (as a .req file) by the customers/distributors as a<br />

request to update their hardware keys. It contains the hardware key details<br />

(such as, the serial number) and the license information.<br />

Update Code<br />

Refers to the code generated by the developer. It defines the actions that you<br />

want to apply on the hardware key. The update code is generated under the<br />

Key Activator tab of the Toolkit.<br />

As a developer, only you have the rights for generating update codes to allow<br />

secure remote update.<br />

Note: An update code can also be generated using the SFNTCreateUpdatePacket<br />

API function of the Key Programming library.<br />

The update packets created using this function can be applied as a buffer<br />

and saved as a *.upw file to be further applied into the end user token<br />

using either the Secure Update Utility, or the SFNTApplyUpdateCode<br />

function from the Secure Update library.<br />

<strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> Developer’s <strong>Guide</strong> 149

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!