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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 7 – Implementing Secure Licensing<br />

Contents Glossary Index Troubleshooting<br />

Frequently Asked Questions<br />

182 <strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> Developer’s <strong>Guide</strong><br />

<br />

Question 1 - If the application failed to obtain a license in one<br />

attempt, do I need to call the SFNTGetLicense function multiple<br />

times?<br />

We recommend calling SFNTGetLicense a few more times, before exiting the<br />

application. For example, you can call the SFNTGetLicense, despite of<br />

encountering SP_ERR_UNIT_NOT_FOUND error in stand-alone environments<br />

and SP_ERR_NO_LICENSE_AVAILABLE in network environments.<br />

Question 2 - Under which conditions are the AES/ECC algorithms in<br />

the token disabled?<br />

The AES and ECC algorithms are NEVER disabled in the token, unless you<br />

apply the deactivation remote update commands (Deactivate AES algorithms<br />

and Deactivate ECC algorithm). However, under the following<br />

conditions, they appear disabled because the licensing functionality associated<br />

with them has expired and the SFNTQueryFeature API function<br />

returns an error:<br />

When the lease period (based on the expiration date or time you<br />

specified) has been reached.<br />

When the number of executions allowed have finished.<br />

When the time tampering takes place as defined in the cheat counter<br />

scenarios on page 170.<br />

Question 3 - Where can I find the query-response pairs for the AES<br />

feature I created? In which format are these written?<br />

The query-response pairs are available in the header file generated under<br />

the Build Options tab. These are written in the hexadecimal format. You<br />

can convert it into ASCII format using the method described below (sample):

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

Saved successfully!

Ooh no, something went wrong!