Changelog

6.0.6 2026-07-22

Trusted class-definition provenance

• Fixed protected JavaFX FXML startup failures caused by MethodUtil defining its verified Trampoline helper through defineClass(byte[]). Trust now propagates only from VM-verified class or loader provenance, not from class names, paths, packages, or CodeSource strings.
• Added real FXML coverage with fx:controller, property elements, controller injection, and WebView startup, plus regressions for trusted dynamic definitions, two-level propagation, unknown sources, unauthorized JARs, and protected-name replacement.
• Published VLX 1.0.14 runtimes for JDK 11, 17, 21, and 25. JDK 8 remains on VLX 1.0.11.

6.0.5 2026-07-21

JavaFX native runtime integrity

• Fixed Windows JavaFX WebView startup failures (Graphics Device initialization failed / No toolkit found) by placing packaged JavaFX DLLs in vlxjre/bin and aligning the launcher's native library search.
• Extended the encrypted app.p4jx allowlist to external native libraries. JavaFX native files must match exact SHA-256 values regardless of path, and Glass revalidates the actual loaded file; unrecognized or tampered files are rejected.
• Published refreshed Protector4J runtimes for JDK 11, 17, 21, and 25. Supported JavaFX grids passed L5.1-L5.4, covering WebView startup plus tamper rejection for module JARs, jdk.jsobject, and Glass native libraries.

6.0.4 2026-07-21

External module integrity and JavaFX runtime compatibility

• Removed path-based trust for external modules. Every external module JAR must now match an exact SHA-256 allowlist entry embedded in app.p4jx; unrecognized or tampered files are rejected regardless of location.
• Added automatic dependency-closure detection from JavaFX module-info.class and controlled admission of pinned JavaFX and JDK modules, including javafx.media and jdk.jsobject.
• Fixed JavaFX WebView startup and post-boot-layer E818 / ClassFormatError failures across supported JDK trains and platforms with newly released P4JX runtimes.

6.0.3 2026-07-20

JavaFX WebView module compatibility

• Fixed optional jdk.jsobject resolution for supported P4JX runtimes rebuilt from the same JDK/VLX version. Packaging no longer rejects a compatible runtime solely because its complete lib/modules image has different bytes.
• Retained train/platform-specific artifact selection, exact module SHA-256 and module-name validation, and dependency-closure verification after installation.

6.0.2 2026-07-20

JavaFX WebView compatibility

• Fixed JavaFX WebView startup failures by packaging javafx.media together with javafx.web and automatically resolving the exact P4JX-matched jdk.jsobject module when a pruned runtime does not include it.
• Added SHA-256-pinned, version/platform/runtime-bound optional module downloads from the regional public download service. Runtimes that already include the module skip the download.

6.0.1 2026-07-20

JavaFX compatibility

• Fixed startup failures for fat JARs that embed JavaFX runtime classes. Compatibility Apply now keeps embedded JavaFX API, implementation, and JNI bridge namespaces unencrypted, avoiding duplicate ownership with packaged JavaFX modules.
• Improved compatibility diagnostics and multilingual guidance for applications with shaded JavaFX runtimes.

6.0.0 2026-07-20

Protector4J 6.0 is a major release built on a redesigned protection architecture, rather than an incremental update to the 5.x series.

Architecture and protection

• Redesigned the foundational architecture of Protector4J and introduced the new P4JX protection engine.
• Added nearly 100 protection measures across archive generation, class loading, runtime execution, anti-debugging, and artifact integrity.
• Significantly raised the barrier to reverse engineering. The new architecture is designed to make short-term cracking extremely difficult, even with advanced AI-assisted analysis tools.
• Strengthened license requests, runtime downloads, artifact verification, and cross-platform installer security.

Product experience

• Added support for JDK 8, 11, 17, 21, and 25, with graphical packaging workflows for Java, JavaFX, Spring Boot, and Tomcat applications.
• Added compatibility scanning, selective class encryption, dependency JAR protection, YAML task import/export, and batch builds for multiple target platforms.
• Redesigned the desktop interface with support for 11 languages and persistent language preferences.

Migration notes

Protector4J 6.0 differs substantially from earlier versions. Please read the latest documentation before using it, and rebuild and migrate your encrypted applications to 6.0 as soon as practical to benefit from the stronger protection.

Download Protector4J 6.0

Earlier releases