-
Bug
-
Resolution: Fixed
-
P2
-
6u18, 6u21
-
b05
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2198935 | 7 | Andy Herrick | P2 | Resolved | Fixed | b104 |
Mixed code protection prohibits mixing signed and unsigned jars in the same JNLP.
Therefore progress jars also need to be signed.
However, even if signed with same certificate they seem to be validated independently of other jars,
i.e. if certificate has never been permanently accepted then user will see 2 different dialogs requesting permissions for the same certificate.
Therefore progress jars also need to be signed.
However, even if signed with same certificate they seem to be validated independently of other jars,
i.e. if certificate has never been permanently accepted then user will see 2 different dialogs requesting permissions for the same certificate.
- backported by
-
JDK-2198935 Custom progress: signed progress cause extra security dialog
-
- Resolved
-
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-