Bug 1481947
| Summary: | Update java-1.8.0-openjdk to 8u144 to fix zip regression [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | java-1.8.0-openjdk | Assignee: | Andrew John Hughes <ahughes> |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | ahughes, bodavis, dbhole, jvanek, lmanasko |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | java-1.8.0-openjdk-1.8.0.144-0.b01.el7_4 | Doc Type: | Bug Fix |
| Doc Text: |
Update 141 of OpenJDK 8 introduced a behavioural change which required directory entries in JAR files to end with a trailing slash. As a consequence, verification of some JAR
files failed, leading to the following
error message:
java.lang.SecurityException: digest missing for <class>
This update upgrades the OpenJDK 8 packages to update 144, which allows the behaviour to be toggled using the -Djdk.util.zip.ensureTrailingSlash option. By default, OpenJDK 8 now follows the legacy behaviour of performing the search again with a trailing slash added to the name, before
reporting that the file cannot be found. As a result, JAR files are now verified as they were before update 141.
|
Story Points: | --- |
| Clone Of: | 1477855 | Environment: | |
| Last Closed: | 2017-09-05 11:32:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1477855 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-08-16 06:34:08 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2591 |