Bug ID: JDK-8172986 Allow --add-opens option for JNLP signed all permission apps

Type: Bug
Component: deploy
Affected Version: 9

Priority: P3
Status: Resolved
Resolution: Fixed

Submitted: 2017-01-18
Updated: 2017-02-09
Resolved: 2017-01-20

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 10	JDK 9
10Fixed	9 b155Fixed

--add-exports is allowed for signed all-permissions apps.  Existing apps using reflection to access non-public members would need --add-opens option too.

`-���add-opens` allows setAccessible to call on non-public members and setAccessible continues to require a security permission check.

The implementation of --add-exports is that it is allowed as a secure vm-arg as far as the native code and relaunch java code is concerned, but an exception is thrown (from Applet2Manager for non-jnlp applets) and from LaunchDesc (for jnlp applications, applets, and JavaFX apps) whenever an app requesting this argument is set to run in the sandbox (not an all-0permissions app). It will be trivial to add --add-opens to this list that currently has only the one arg. Note that although there are two legal forms of these arg (using either an equals sign or space) deployment only supports the equal sign usage (--add-exports=XXX) due to the way vm-args are parsed we cannot support the case using a space (--add-exports XXX). The same will be the case for --add-opens.

19-01-2017

Duplicate :	JDK-8173166 - New --add-opens VM option is not taken into account in WebStart app
Relates :	JDK-8153077 - Allow -XaddExports be specified via the java-vm-args attribute