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

More documents

Recommendations

Info

Chapter 6 – Secure Remote Updates Contents Glossary Index Troubleshooting 164 Sentinel Hardware Keys Developer’s Guide Because the Secure Update Wizard is integrated with the CodeCover/APIprotected application at the license designing stage, its interface can be customized to include your product and company-specific information (like, product name, version, and copyright), text (like, e-mail address and content) and images (like, splash image and application icon). Question 3 - What are the steps that a customer undergoes to activate the application using Secure Update Wizard? The topic “Walk-through of Secure Update Wizard (Screens)” in the Sentinel Keys Toolkit Help describes these steps. Question 4 - Apart from the Sentinel Key and my application, what other files I need to ship along with my protected application? Please refer to Chapter 10, “Redistributables for Customers and Distributors,” on page 223 for complete information. Question 5 - Can I use the same request code (.req) file to generate an update code (.upw) file, and a license addition (.nlf) file? No, you are not advised to do so, because when the request code is generated, the value of device update counter is stored in the *.req file. which is incremented every time you follow any of the following operations on the token: Formatting before adding new licenses using *.nlf file. Updating cheat counter value. Updating Last known date and time (LKDT) value, once the lease operation has been performed. Updating user limit value. Now, consider a scenario wherein you applied the *.req file to generate a *.upw file, and later used the same *.req file to generate the *.nlf file. The device update counter value in the *.req file may not match its value on the token if you have performed any of the operations listed above, hence restricting the process of applying the license addition code (*.nlf) file.
Frequently Asked Questions Contents Glossary Index Troubleshooting Question 6 - Can Secure Update Utility of version 1.0 apply the .upw file generated by SHK1.2.1 and higher? No, since the .upw file generated by Sentinel Hardware Keys version 1.2.1 and higher will not be applied using the Secure Update library of version 1.0, please ensure that you distribute the latest Secure Update Utility and associated DLLs to your customer/distributor. Question 7 - If I select Delete all licenses from token while generating *.nlf file, will the end user be able to apply this file on the token as many times as he/she wants? No, the new license can be added only once by applying the license addition (.nlf) file. Question 8 - What is the role of Device Update Counter value in removing all licenses from the token? In what scenarios its value is updated? Device Update Counter is the global update counter in the end user token which is incremented every time all licenses from the token are deleted. Its value is also updated in the following scenarios: Cheat counter value updates. Last known date and time (LKDT) updates, once the lease operation has been performed. User limit value updates. Question 9 - In case of Bidirectional Updates, which factors should be taken in consideration before generating the update code for a feature? The ISV’s should ensure that one Update file shall contain a single update action because the update actions of conflicting nature should not be applied with each other. The list of such update actions is provided below: Counter Increment Counter Overwrite Counter Sentinel Hardware Keys Developer’s Guide 165
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:
Page 69 and 70:
Chapter 3 Planning Application Prot
Page 71 and 72:
About Features, Templates, and Grou
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Planning Application Protection and
Page 81 and 82:
Page 83 and 84:
Enabling License Sharing Planning A
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91:
Part 2 Designing and Implementing P
Page 94 and 95:
Chapter 4 - Protecting Applications
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133: Chapter 5 - Protecting Applications
Page 156 and 157: Chapter 6 - Secure Remote Updates C
Page 186 and 187: Chapter 7 - Implementing Secure Lic
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: Frequently Asked Questions Contents
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?