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.

Chapter 4 – Protecting Applications Using CodeCover<br />

Contents Glossary Index Troubleshooting<br />

used to run the application. Though this step is optional for adding a Code-<br />

Cover feature, and by default all files, other than .exe, .dll, and .bpl, you<br />

selected under the Files tab, will be encrypted.<br />

To specify the file encryption settings:<br />

1. Click the Change the file encryption options link in the Add<br />

CodeCover Feature dialog box. The CodeCover file encryption<br />

settings dialog box appears.<br />

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

<br />

2. Select the Encrypt/decrypt the following files at run-time check<br />

box. Now, type the file extensions in the edit field. This field can contain<br />

up to 255 characters. You can filter files using the wildcard symbols<br />

asterisk (*) and semicolon (;). The 8.10 naming convention is<br />

followed, meaning that the file name and extension cannot exceed 8<br />

and 10 characters, respectively. File filters like, *.*, *name.* are not<br />

acceptable. Given below is a description of the valid conventions:<br />

Providing Files for Encryption/Decryption<br />

Convention Example<br />

*.extension *.txt will encrypt/decrypt files. For example,<br />

settings.txt and install.txt.<br />

name*.* safe*.* will encrypt/decrypt files. For example,<br />

safeobj.htm and safenet.cpp.<br />

name*.extension safe*.txt will encrypt/decrypt files. For example,<br />

safeobj.txt and safenet.txt.<br />

3. The Toolkit automatically generates an encryption seed. If you want<br />

to provide your own encryption seed, select the Specify my own<br />

encryption seed check box and edit the value. Please note that if the<br />

encrypted data files are shared by multiple applications, all the applications<br />

must use the same encryption seed. The seed can consist of<br />

two strings of 14 hexadecimal characters each (forming a 112-bit<br />

long seed).<br />

4. Click OK. You are returned to the Add CodeCover Feature dialog<br />

box.

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

Saved successfully!

Ooh no, something went wrong!