PELock v2.02 – Anti Cracking Solution

PELock v2.02 was released. PELock is an advanced anti cracking solution for Windows applications with built-in license key system with SDK API support for C/C++, D, Delphi, PureBasic, PowerBASIC & MASM applications.

PELock Protection SDK Settings

List of changes:

  • removed a bug that caused crashes while adding virtual DLL libraries to the list
  • fixed DLL handling bug with the default configuration settings
  • callbacks parameter passing is fixed for stdcall convention

Full changelog – https://www.pelock.com/products/pelock/history

Download - https://www.pelock.com/products/pelock/download

Software Licensing SDK

PELock is a software security solution designed for protection of any 32 bit Windows application against cracking, modifications and reverse engineering analysis.

https://www.pelock.com/products/pelock

Advanced software protection settings

Licensing SDK

You can closely integrate the protection and licensing features using dedicated SDK with hundreds of examples for

  • C/C++
  • Delphi, Lazarus
  • Freepascal
  • PureBasic
  • PowerBASIC
  • D
  • Assembler

SDK & usage examples is available now also at GitHub:

https://github.com/PELock/PELock-Software-Protection-and-Licensing-SDK/

Protection and Licensing SDK settings

License Key Manager

PELock comes with a built-in licensing system, you can use it to easily add license key system for your application.

License key manager

Adding new license

Time trial settings

You can also set various time-trial limitations for the protected application, e.g. 30 days trial.

Time trial settings

Virtual DLL binder

PELock has a built-in binder for additional application DLL libraries, it’s possible to merge your main application EXE file with any number of extra DLL libraries into single output EXE file.

Virtual DLL binding

If your application uses or requires an additional DLL libraries you can hide them inside the protected application, no third party will be able to view it, nor any other program will have access to it, because the whole loading process is emulated in the memory and nothing is written to disk, and it’s completely transparent to the application working.