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

More documents

Recommendations

Info

Appendix D – Migration from SuperPro and UltraPro Contents Glossary Index Troubleshooting Sentinel Dual Hardware Keys are available for stand-alone and network versions. 280 Sentinel Hardware Keys Developer’s Guide Sentinel Dual Hardware Keys have 256 cells of memory for use by your SuperPro or UltraPro implementation so you will receive a new model number with your kit. 2. Program Sentinel Dual Hardware Keys with the same protection strategy you prepared for SuperPro or UltraPro Keys. SuperPro developers can straightaway program Sentinel Dual Hardware Keys with the protection strategy they prepared for SuperPro Keys. However, Sentinel UltraPro developers need to make a small modification (described below) before they program the design into Dual Keys. Note that in stage 1 you need not do any modifications in the application code or API implementation: In the Protection Manager screen, select the project form the drop-down list that has your design. Select the design in the Designs list and note down its design ID (shown in top-middle of the Protection Manager screen). Click the Duplicate button shown next to the Designs panel. The Duplicate Design dialog box appears. Modify the design name, as two designs with same name cannot co-exist in a project. Click OK. Select the duplicated design and right-click to open a short-cut menu. Select the option to view design properties. The Design Properties dialog box appears. Modify the design ID of the duplicated design same as the existing design. Click OK.
Stage 2 - Design New Protection Strategy Contents Glossary Index Troubleshooting Attach the Sentinel Dual Hardware Key to a USB port/hub on your system. Click the Build button to prototype the duplicated design. 3. Distribute the latest Sentinel System Driver with your protected application to support Sentinel Dual Hardware Keys. You may allow the driver to be downloaded from your Website. A copy can be downloaded from SafeNet Website (http:// www.safenet-inc.com/support/ tech/sentinel.asp). Stage 2 - Design New Protection Strategy In stage 2, you will be implementing a new protection strategy using the Sentinel Keys Toolkit. This can ideally be done for the upcoming releases of your software. You need to: 1. Order the Sentinel Hardware Keys development kit through your Sentinel sales representative. 2. After installation, use the Sentinel Keys Toolkit to implement superior CodeCover and/or high-level Business Layer API protection-including AES-based encryption/decryption and ECC-based signing/verification. Note: You will NOT be able to import/re-use your legacy API or CodeCover Super- Pro or UltraPro code base (prepared using Sentinel SuperPro or UltraPro kits) in the Sentinel Keys Toolkit. Since the Sentinel Hardware Keys use the latest security technologies, you will need to implement your new, highly secure protection strategy from scratch. Existing (Stage 1) Customers Who Want to Upgrade - You can upgrade the existing customers to the latest version of your software remotely, without shipping new hardware keys. 1 The Sentinel Dual 1. The upgrade licenses can be generated using a higher version of Sentinel Keys Toolkit (to be released later in this year). Sentinel Hardware Keys Developer’s Guide 281
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:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Chapter 6 - Secure Remote Updates C
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
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: Chapter 10 - Redistributables for C
Page 262 and 263: Appendix A - Troubleshooting Conten
Page 276 and 277: Appendix B - Glossary Contents Glos
Page 296 and 297: Appendix C - Sentinel Keys Hardware
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 ...

Create successful ePaper yourself

Delete template?

Save as template?