API Implementation
- Meaning of “Implementation with API”
- Recommended Steps for Protecting Applications with API
- Smarx®OS as the Basis for the CRYPTO-BOX Integration
- Smarx®OS API Subsets
- Using the Smarx®OS API under Different Environments
- Static Libraries (C/C++, Delphi)
- Dynamic Libraries (DLL)
- .NET
- COM/ActiveX
- Library and Sample Code for Your Environment
- Library and Samplecode from the Protection Kit
Dynamic Libraries (DLL)
Dynamic libraries (DLLs) provide a simple, but less secure link.
DLL-based implementation should be considered only when no other options can be used (static library, COM).
If you use DLL, try to improve the level of protection and licensing logic for your application. This is possible with the help of hardware-based
- encryption,
- storing important data in the CRYPTO-BOX or
- using parallel threads, etc.
This makes it difficult to emulate this logic by replacing the DLL.
DLLs are provided for all Windows platform environments (x86 and x64). For the Visual Basic 6.0 environment there is a special DLL (CBIOSVB6.DLL).
IMPORTANT NOTE:
| The Smarx OS CBIOS API Reference contains a detailed description of the API calls within the CBIOS API and the CBIOS Network API for developers working with Visual Basic. |