Guides

Runtime Protection

Add runtime checks

Configure debugger guards, integrity checks and class protection. These controls affect the protected application at runtime and remain separate from build-time bytecode verification.

Configuration

These entries belong in the engine block of your RR configuration.

engine ^ {
  antiDebug false;
  selfVerify true;
  runtimeIntegrity false;
}

Choose checks for your environment

Debugger guards can affect diagnostics and development tools. Integrity checks can reject changes made after protection. Enable the checks that match how you distribute and run your application.

Option reference

Anti Debug Injection

boolean

antiDebug

Injects runtime debugger checks. Test compatibility with diagnostics and the intended release environment.

Panel default false

Integrity Verification

boolean

selfVerify

Enables engine self-verification. Repacking protected output can affect integrity checks.

Panel default true

Runtime integrity

boolean

runtimeIntegrity

Enables runtime integrity checks independently of self-verification.

Panel default false

Runtime anti analysis

boolean

runtimeAntiAnalysis

Enables runtime analysis guards. Test compatibility with monitoring and diagnostic tools.

Panel default false

Native guard

boolean

nativeGuard

Enables the native guard. A matching native runtime is required.

Panel default false

Class Encryption

boolean

classEncryption

Enables class encryption in supported profiles. Test class loading with the packaged runtime.

Panel default false

Runtime Protection

Configuration

Choose checks for your environment

Option reference

Related guides