Bug 1659497 - Updated krb5-libs packages in RHEL 7.6 will cause apps to crash when fips mode is on [rhel-7.6.z]
Summary: Updated krb5-libs packages in RHEL 7.6 will cause apps to crash when fips mod...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Robbie Harwood
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On: 1645711
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-14 14:30 UTC by RAD team bot copy to z-stream
Modified: 2019-01-29 17:23 UTC (History)
3 users (show)

Fixed In Version: krb5-1.15.1-37.el7_6
Doc Type: Bug Fix
Doc Text:
Previously, Red Hat Enterprise Linux 7.6 build of the krb5 system increased compliance with FIPS-140. As a consequence, certain previously permitted configurations that were prohibited by FIPS-140 stopped working. with this update, the changes have been reverted, because krb5 only needs to work in the FIPS mode, not be FIPS compliant. As a result, RHEL 7.6.z should work in the same way RHEL 7.5 did. Please note that Red hat Enterprise Linux 8 does not support these configurations at the moment.
Clone Of: 1645711
Environment:
Last Closed: 2019-01-29 17:23:24 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0183 None None None 2019-01-29 17:23:25 UTC

Description RAD team bot copy to z-stream 2018-12-14 14:30:38 UTC
This bug has been copied from bug #1645711 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 6 errata-xmlrpc 2019-01-29 17:23:24 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-2019:0183


Note You need to log in before you can comment on or make changes to this bug.