-
Bug
-
Resolution: Fixed
-
P1
-
7u51, 8
-
b03
-
b05
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8027248 | 8 | Andy Herrick | P1 | Closed | Fixed | b114 |
| JDK-8034450 | 7u65 | Andy Herrick | P1 | Resolved | Fixed | b01 |
| JDK-8027340 | 7u60 | Andy Herrick | P1 | Resolved | Fixed | b01 |
| JDK-8027401 | 7u55 | Andy Herrick | P1 | Resolved | Fixed | b01 |
The latest UE flow for 7u51: http://aseng-wiki.us.oracle.com/asengwiki/display/ASUsability/Summary+of+Tighter+JRE+Security+Dialogs#SummaryofTighterJRESecurityDialogs-JDK7u51%28Jan2014%29
introduces (for the first time) differant behavior for self-signed cert as for expired cert.
The implementation treats them the same, as SecuritySettings.isExpiredAllowed() simply returns the value for isSelfSignedAllowed(). This was OK in past (since value was always the same) but now we need to have seperate entry in the table for self signed and expired, since their behavior is no longer the same at all security levels.
introduces (for the first time) differant behavior for self-signed cert as for expired cert.
The implementation treats them the same, as SecuritySettings.isExpiredAllowed() simply returns the value for isSelfSignedAllowed(). This was OK in past (since value was always the same) but now we need to have seperate entry in the table for self signed and expired, since their behavior is no longer the same at all security levels.
- backported by
-
JDK-8027340 [regression] Applications with Permissions attriburte signed with expired certificate are blocked on High security level
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-