-
Bug
-
Resolution: Fixed
-
P2
-
7u40
-
b34
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8020422 | 8 | Andy Herrick | P2 | Closed | Fixed | b99 |
| JDK-8034314 | 7u65 | Andy Herrick | P2 | Resolved | Fixed | b01 |
| JDK-8020574 | 7u60 | Andy Herrick | P2 | Resolved | Fixed | b01 |
| JDK-8021020 | 7u45 | Andy Herrick | P2 | Closed | Fixed | b04 |
The initialization of LSP occurs too soon in both javaws and plugin causing lots of problems:
1.) it is initialized before proxies are initialized, so if it is valid policy jar with re vocation checking on, cannot use proxies to reach the OCSP.
2.) it is initialized before trace is initialized, so we cannot see Trace statements related to parsing lsp file.
3.) it is initialized in javaws when launch javaws for reasons other than running an app:
javaws -viewer, javaws -import, javaws - SSVBaselineUpdate, etc.
in all the above cases, revocation checking of a valid policy file may have to timeout before the operation can proceed.
1.) it is initialized before proxies are initialized, so if it is valid policy jar with re vocation checking on, cannot use proxies to reach the OCSP.
2.) it is initialized before trace is initialized, so we cannot see Trace statements related to parsing lsp file.
3.) it is initialized in javaws when launch javaws for reasons other than running an app:
javaws -viewer, javaws -import, javaws - SSVBaselineUpdate, etc.
in all the above cases, revocation checking of a valid policy file may have to timeout before the operation can proceed.
- backported by
-
JDK-8020574 LSP: LocalSecurityPolicy is initialized too soon
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
-
- Closed
-
-
-
- Closed
-
(1 duplicates)