JDK-8131070 : re enable secure launcher for cross platform launches.
- Type: Bug
- Component: deploy
- Sub-Component: webstart
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-07-13
- Updated: 2018-02-22
- Resolved: 2015-08-11
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.
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 8 | JDK 9 |
|---|---|
8u102Fixed  |
9 b80Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The initial implementation of JDK-8003984 will disable using the secure launcher when cross launching from 32 to 64 bit (or 64 to 32 bit) architecture in JnlpxArgs.execProgram.
This is because secure launcher will reject launching when jp2launcher.exe is invoked from a jp2launcher.exe process with a different path (one is 32 bit and the other is 64 bit)
clutter.cpp code in JWC_IsParentTrusted() needs to be updated to handle this scenerio, then the two lines in Jnlpxargs.execProgram:
" if (!crossArch && Config.useSecureLaunch(jreInfo)) {" can be restored to:
"if (Config.useSecureLaunch(jreInfo)) {"
Comments
|