-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b80
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8135370 | emb-9 | Alexander Matveev | P3 | Resolved | Fixed | team |
| JDK-8156236 | 8u111 | Alexander Matveev | P3 | Resolved | Fixed | b01 |
| JDK-8150058 | 8u102 | Alexander Matveev | P3 | Resolved | Fixed | b01 |
| JDK-8162011 | emb-8u111 | Alexander Matveev | P3 | Resolved | Fixed | b01 |
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)) {"
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)) {"
- backported by
-
JDK-8135370 re enable secure launcher for cross platform launches.
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8003984 Allow relaunch between 32 / 64 bit versions in Java Web Start when you have latest versions of both
-
- Resolved
-
-
-
- Resolved
-
(1 relates to)