-
Bug
-
Resolution: Fixed
-
P3
-
6u10
-
b24
-
generic
-
windows
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2199266 | 7 | Andy Herrick | P3 | Resolved | Fixed | b64 |
[1] - App signed with expired certificate
[2] - App requires prev version of JRE (Eg: 1.5.0)
[3] - Launch App using latest JRE from command line
[4] - It will show warning-dialog
[5] - Once you accept it, application will be launched
In previous releases, at step [4], the warning dialog is shown using JRE on which the application is to be executed. But now its done using latest JRE. Validation and warning-dialog must be done using JRE on which the application is to be executed.
Test jnlp
http://nicole1.sfbay.sun.com:8080/JavawsMustangIntegTest/ssv/test_signed_1.5.0.jnlp
[2] - App requires prev version of JRE (Eg: 1.5.0)
[3] - Launch App using latest JRE from command line
[4] - It will show warning-dialog
[5] - Once you accept it, application will be launched
In previous releases, at step [4], the warning dialog is shown using JRE on which the application is to be executed. But now its done using latest JRE. Validation and warning-dialog must be done using JRE on which the application is to be executed.
Test jnlp
http://nicole1.sfbay.sun.com:8080/JavawsMustangIntegTest/ssv/test_signed_1.5.0.jnlp
- backported by
-
JDK-2199266 Security dialog popped up using latest JRE instead of JRE on which application is to be executed
-
- Resolved
-