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
Automatic Protection and Implementation with API
If you protect your software with the CRYPTO-BOX, you have two basic options:
- Automatic protection of your compiled executable - see separate AutoCrypt Application Notes for more information.
- Implementation in the source code of your application via API.
Implementation in the source code via API is aimed at developers who require maximum security and flexibility for their applications.
API offers a product-specific and highly efficient protection strategy that you can integrate, for example, to support demo and full versions of the program, online function activation, remote update scenarios and much more.
INFO
| It is possible to combine both AutoCrypt and API implementation if, for example, you want to use the encryption options offered by AutoCrypt. Or you can consider AC API which combines the simplicity of AutoCypt with the flexibility of API implementation. This is especially useful if your application type is not compatible with the AutoCrypt Wrapper. See here for more details. |