Bug 1719465

Summary:	Removal of component Frr or its crypto from RHEL
Product:	Red Hat Enterprise Linux 8	Reporter:	Simo Sorce <ssorce>
Component:	frr	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED ERRATA	QA Contact:	Daniel Rusek <drusek>
Severity:	urgent	Docs Contact:	Marie Hornickova <mdolezel>
Priority:	high
Version:	8.1	CC:	blc, drusek, mruprich, mthacker, pmosko, psklenar, ssorce, thozza, wchadwic
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	frr-7.0-5.el8	Doc Type:	Known Issue
Doc Text:	Cause: The EIGRP MD5 authentication is currently broken and cannot be used. The SHA-256 authentication was never working in the first place. Consequence: If you try to use MD5 authentication between routers, it will break the neighborship between the EIGRP routers. The SHA-256 never worked, neither in quagga nor in frr(https://github.com/FRRouting/frr/issues/4129). Workaround (if any): There is currently no workaround. Result:	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 21:09:48 UTC	Type:	Bug
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:
Bug Blocks:	1635116, 1657029, 1724835

Description Simo Sorce 2019-06-11 21:22:29 UTC

This component brings new implementations of cryptographic algorithms in RHEL, which affects the manageability and consistency of the operating system, and voids our message on the operating system’s FIPS140-2 certification and compliance. This bug is about removing this component from RHEL, and any dependent applications should be modified to depend on RHEL core crypto libraries (see 
https://access.redhat.com/articles/3359851 )


This component implements HMAC-SHA256 and HMAC-MD5

Comment 1 Simo Sorce 2019-06-11 21:24:24 UTC

Brenadan you may want to add this bug to your list of certification blockers

Comment 25 errata-xmlrpc 2019-11-05 21:09:48 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/RHEA-2019:3427