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

More documents

Recommendations

Info

Chapter 4 – Protecting Applications Using CodeCover Contents Glossary Index Troubleshooting Default Feature Instance Settings (Continued) Item Description Default Setting Expiration time Specify an expiration time (in minutes). 14400 minutes (10 days) Execution count Specify an execution count for running the protected application. 80 Sentinel Hardware Keys Developer’s Guide Note: If you specify both the licensing controls—lease and limited executions—the application will expire as soon as any of these limits is reached. 4. Selecting the Add instances later check box will allow you to add new feature instances later in the License Manager screen. This option helps in modifying the "licensing values" without modifying the "licensing implementation" in the application/code. For example, the programmer who implemented the application protection had set the expiration date as "10/10/05" and also selected this check box. Later, if desired, the marketing/key programming personnel can modify it to suit some customer's requirement (such as, 10/10/07) and program the Sentinel Key. This does not require you to apply the CodeCover protection again, modify the API calls, or repackage the product. You can now specify the networking settings (such as, the access mode, license sharing, and maintain license time interval) under the Networking tab. Providing Networking Settings To provide the networking settings: 1. Click the Networking tab in the Add CodeCover Feature dialog box. 1
2. Specify options using the information below: Access Mode License Sharing Providing Networking Settings Contents Glossary Index Troubleshooting CodeCover Networking Settings Item Description Default Setting Maintain license time Terminal Client Specifies the access mode to find the Sentinel Key. Specifies whether license sharing is enabled or disabled. Sets the interval for which the Sentinel Keys Server maintains the license. Allows you to protect an application in a Terminal Service environment. This option is enabled only in stand-alone mode. It is not available in network mode as remote client services are already ON for network applications. STANDALONE (Stand-alone mode) OFF (License sharing not allowed for network users) 120 seconds. If you do not modify the default value, license time/heartbeat interval (if specified) in the configuration file will override it. OFF (Terminal Client service is disabled for stand-alone applications by default). Setting this option to ON enables Terminal Client Services for CodeCoverprotected applications, in stand-alone mode. For API-protected applications, you need to call the SFNTGetLicense function with the SP_ENABLE_TERMINAL_CLIENT flag (in API Explorer). Sentinel Hardware Keys Developer’s Guide 81
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 148 and 149:
Chapter 5 - Protecting Applications
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:
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 ...

Create successful ePaper yourself

Delete template?

Save as template?