JDK-8175250 : Manifest checking throws exception with no entry
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 9
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2017-02-20
- Updated: 2017-03-20
- Resolved: 2017-02-22
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 10 | JDK 8 | JDK 9 |
|---|---|---|
10Fixed  |
8u152Fixed |
9 b159Fixed |
Related Reports
|
Relates :
|
Description
Current code will throw an exception if there is no attribute entry in the manifest, This wasn't obvious in testing because DIGEST-MANIFEST entries are very common. It took JCE provider testing that checked DIGEST-MAIN-ATTRIBUTE entries to show the bug. The fix is simple and silly logic mistake.
Comments
|