Protect JavaSE App

GUI Tool

Execute protector4j-ui[.exe] in the tool's directory, you will see the interface below

Login

If you have got the license, you can click the login button on the top-right corner and input your account information. Although, without the license, you can have a test too.

Choose app type

Click the "JavaSE Application" button on the app types page.

Choose jars to protect

Choose the jars files to protect, you can add single or multi jar files.

Choose classes to protect

Choose the classes to protect. On this page, you can just choose some key classes to encrypt or encrypt all classes in the jar file. The classes in the embed jar files are not supported to be encrypted now, they will keep as they are.

Output options

On this page, you can specify the Java version, the Output folder, and the Temp folder. After this is done, click the "Start" button on the bottom, it will start the encryption process.

Encryption process

It will take some time to finish the encryption process. After it is done, you can check the result in the output folder.

Check the result

After the encryption process complete, please go to the output folder to check the result. The encrypted jars and the custom java runtime are in there.

Run the encrypted app

You should use our custom java runtime to run the encrypted app, go the output folder and execute:

jre/bin/java -jar xxx.jar

Every encryption task will request a new and unique key. The files that are been encrypted in different task can not be used together.

CLI Tool

The configuration of task file

Please find the java.generic.json in the tool's directory, copy and modify a new one.

{
"email" : "",
"password" : "",
"jarsPath" : [ ],
"protectAll" : false,
"outputFolder" : "",
"tempFolder" : "",
"classesToProtect" : [ ],
"javaVersion" : ""
}

The account information

If you have purchased our product, you would have got your account information including the email address and the password for the license. Please type them in the appropriate fields, the value of the password field should be the md5 value of the password, not the password itself. or you can leave the email and the password fields empty, just have a try to this tool.

"email" : "",
"password" : "[md5-of-password]",

Specify the jars and the classes need to be encrypted.

jarsPath

The jarsPath field is an array, which you could specify one or multi jar files that need to be processed in the encryption work.

"jarsPath" : ["path-to-jarfile1","path-to-jarfile2"],

Please use "\" as path seperator in Windows, as "C:\users\vlinx\jprotector", don't use "\"

protectAll

If this value is true, all the classes in the jar will be encrypted. But The classes in the embed jar files are not supported to be encrypted now, they will keep as they are.

classesToProtect

In this field, you can specify the classes that need to be encrypted. It can be a full class name, or wildcard- case ones, just like:

"classesToProtect" : [
"vlinx.test.TestClass1",
"vlinx.test.pack1.*",
"vlinx.test.pack1.**"
],

* means all the classes in the package, but exclude the classes in the subpackage

** means all the classes in the package including the classes in the subpackage.

If the protectAll is true, this field will be ignored.

The classes in the embed jar files are not supported to encrypted now, they will keep as they are

javaVersion

The java versions supported now are Java 8 and Java 11, you can type "java-8" for Java 8 and type "java-11" for Java 11

tempFolder

The temp folder for the files generated during the encryption process, after the task completed, the files in the temp folder will be cleaned.

outputFolder

The encrypted app and the custom Java runtime will be placed into the output folder.

Execute the encryption process

Go the tool's directory and execute the command below to runthe encryption process

protector4j -t java -f path-of-task-file

-t task type

-f task file

protector4j --help` to see the detail arguments.

Check the result

After the encryption process, please go to the output folder to check the result. The encrypted jars and the custom java runtime are in there.

Run the encrypted app

You should use our custom java runtime to run the encrypted app, go the output folder and execute the command below

jre/bin/java -jar xxx.jar

Every encryption task will request a new and unique key. The files that are been encrypted in different task can not be used together.