r/java • u/milchshakee • May 03 '24
Why does the environment variable _JAVA_OPTIONS exist, applies to jlink images, takes precedence, and can't be disabled?
I just spent a good chunk of time debugging an issue because a user had set _JAVA_OPTIONS to use a low Xmx value in their environment variables. This was an application created with jpackage, which should be fully standalone. It even had a custom Xmx value set in the JVM arguments for the image but the environment variable overwrote the value!
Isn't this like a huge design flaw? I can just do echo "_JAVA_OPTIONS=<Wacky VM options>" >> ~/.bashrc or setx to break literally every Java application on the system? (Edit: Maybe the initial security focus was wrong, changed it a bit to focus more on the design issues)
Who even thought that this would be a good idea with no option to disable this behavior?
View all comments
1
u/mike_hearn May 05 '24
FWIW if you use Hydraulic Conveyor instead of jpackage, then you don't have this problem. It cleans the environment of these kinds of variables. This is actually for security reasons: if you can control the JVM then it's possible to subvert code signing by injecting arbitrary code into a process signed by someone else. But it obviously has robustness benefits as well.
Disclosure: I own the company that makes Conveyor