Java Considerations

When protecting Java executables, consider the following issues:

>The methods selected for protection by Sentinel LDK Envelope by default are not the optimal choices for your application or library. You must review and modify the list of selected methods to provide the best mix of security and performance. For more information, see the description of optimizing protection settings in the Sentinel LDK Envelope for Windows.

>Sentinel LDK Envelope does not support protection of Java paint methods, but it allows you to select them in the user interface. As a result, the protected application may cause a deadlock when it executes a protected paint method at runtime with no Sentinel protection key connected. To prevent this issue from occurring, you can deselect all paint methods. Note that paint methods do not usually contain application logic; therefore, deselecting them typically has no impact on security. As an alternative, you can select console output for messages by enabling stderr output instead of windows in the Advanced settings panel.

>When you test Sentinel LDK Envelope for the first time with your application, it is recommended that you clear the default selection and start with the protection of a single method that you want to protect. After you protect the method, test your application. If the application works as expected, continue to protect additional methods and test after each addition until you have reached the desired protection selection for the application. Do not try to apply this selection to different applications.

>Sentinel LDK Envelope does not support protection of methods that use the Hibernate service.

>Sentinel LDK Envelope does not support protection of methods that, in turn, use Synthetic methods that are created as bootstrap methods or as arguments of bootstrap attributes.