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

More documents

Recommendations

Info

Chapter 4 – Protecting Applications Using CodeCover Contents Glossary Index Troubleshooting 96 Sentinel Hardware Keys Developer’s Guide The license template to be programmed into the Custom CodeCover key must have at least one CodeCover feature. The features other than CodeCover (if present) are ignored. Each Custom CodeCover key has an validity date (called global lease date) that specifies the date till when this key can be used for protection. Creating Custom CodeCover Key A Custom CodeCover key is created using the Custom CodeCover Key tab on the License Manager screen of the Sentinel Keys Toolkit. The Custom CodeCover Key Tab 1. Attach the Sentinel Key that you want to initialize as Custom Code- Cover key to a USB port. Attach a developer key of the same developer
CodeCover Protection using Custom CodeCover Key Contents Glossary Index Troubleshooting ID as that of Sentinel Key. Make sure to select the Sentinel Key in the Key Status panel. Note: Make sure to attach only one Sentinel Key. 2. On the License Manager screen, load the group containing the license templates that you want to program into the Custom Code- Cover key. Select the license(s) having at least one CodeCover feature; and if required further select the CodeCover features you want to program into the Custom CodeCover Key. Note: While creating Custom CodeCover key, the Toolkit ignores API features (if any) in the selected license templates. Only CodeCover features are programmed into the Custom CodeCover key. 3. Click the Custom CodeCover Key tab on the License Manager screen of the Toolkit. 4. Click the date picker icon, and select an Expiry Date till which you want the Custom CodeCover key to remain valid. 5. Click Make CodeCover Key to initialize the attached Sentinel Key as Custom CodeCover key. The “Key programmed” message appears after the Custom CodeCover has been successfully created. Using Custom CodeCover Key An individual (referred to as deployer) uses the Custom CodeCover key and Command-Line CodeCover Utility to protect an application at the customer’s location. The customer can then execute the protected application using his Sentinel Key. The Command-Line CodeCover Utility provides the /CK option that you need to use for protecting files using the Custom CodeCover key. For more details, please see “Using the Command-Line CodeCover Utility” on page 92. Sentinel Hardware Keys Developer’s Guide 97
Page 2 and 3:
Copyright © 2009, SafeNet, Inc. Al
Page 4 and 5:
Certifications European Community D
Page 6 and 7:
FCC Compliance FC Sentinel Hardware
Page 8 and 9:
Contents Sentinel Keys Server .....
Page 10 and 11:
Contents Sending Group Files to Dis
Page 12 and 13:
Contents xii Sentinel Hardware Keys
Page 14 and 15:
Conventions Used in This Guide You
Page 16 and 17:
Technical Support Technical Support
Page 18 and 19:
We Welcome Your Comments Export Con
Page 21 and 22:
Chapter 1 Introduction In this chap
Page 23 and 24:
Sentinel Keys Protect Against Softw
Page 25 and 26:
Sentinel Keys Offer Sophisticated P
Page 27 and 28:
Sentinel Keys Offer Sophisticated P
Page 29 and 30:
The Business Layer API Functions Se
Page 31 and 32:
Programming Utility Sentinel Keys T
Page 33 and 34:
Frequently Asked Questions Contents
Page 35 and 36:
Page 37 and 38:
Chapter 2 Sentinel Hardware Keys SD
Page 39 and 40:
Compiler Interfaces Sentinel Keys L
Page 41 and 42:
Distributor Key Distributor Key Con
Page 43 and 44:
Sentinel Keys Contents Glossary Ind
Page 45 and 46:
Sentinel Keys Contents Glossary Ind
Page 47 and 48:
Sentinel Keys Server Contents Gloss
Page 49 and 50:
Sentinel System Driver Sentinel Sys
Page 51 and 52:
Backward-compatibility Information
Page 53 and 54:
Command-Line CodeCover Utility Cont
Page 55 and 56:
Key Programming APIs Contents Gloss
Page 57 and 58:
GCC a For Linux Compiler/Environmen
Page 59 and 60:
Sentinel Keys License Monitor Conte
Page 61 and 62:
Sentinel Protection Installer Conte
Page 63 and 64: Secure Update API Frequently Asked
Page 65 and 66: authentication.) Frequently Asked Q
Page 67 and 68: Frequently Asked Questions Contents
Page 69 and 70: Chapter 3 Planning Application Prot
Page 71 and 72: About Features, Templates, and Grou
Page 79 and 80: Planning Application Protection and
Page 83 and 84: Enabling License Sharing Planning A
Page 89 and 90: Frequently Asked Questions Contents
Page 91: Part 2 Designing and Implementing P
Page 94 and 95: Chapter 4 - Protecting Applications
Page 156 and 157: Chapter 6 - Secure Remote Updates C
Page 164 and 165:
Chapter 6 - Secure Remote Updates C
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Chapter 7 - Implementing Secure Lic
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 205 and 206:
Chapter 8 License Grouping This cha
Page 207 and 208:
Creating New Groups To create a new
Page 209 and 210:
Duplicating Groups Sending Group Fi
Page 211 and 212:
Creating New Feature Instances Cont
Page 213 and 214:
Export-File Manager Export-File Man
Page 215 and 216:
For a Loaded Group Frequently Asked
Page 217 and 218:
Update Existing Licensing Values Fr
Page 219 and 220:
Stand-alone License Manager Frequen
Page 221 and 222:
Chapter 9 Programming Sentinel Hard
Page 223 and 224:
Programming Sentinel Keys using Sen
Page 225 and 226:
To create an .wps file: Programming
Page 227 and 228:
Programming Sentinel Keys using the
Page 229 and 230:
Programming Sentinel Keys using the
Page 231 and 232:
Page 233 and 234:
Utility/Executable developed out of
Page 235 and 236:
Page 237 and 238:
Page 239:
Part 4 Distributing Protected Appli
Page 242 and 243:
Chapter 10 - Redistributables for C
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Appendix A - Troubleshooting Conten
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Appendix B - Glossary Contents Glos
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Appendix C - Sentinel Keys Hardware
Page 298 and 299:
Appendix D - Migration from SuperPr
Page 300 and 301:
Appendix D - Migration from SuperPr
Page 302 and 303:
Index Contents Glossary Index Troub
Page 304:
Index Contents Glossary Index Troub
show all

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

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

Delete template?

Save as template?