Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1613833

Summary:	[RFE] - Use SHA256 for engine-backup
Product:	[oVirt] ovirt-engine	Reporter:	Yuval Turgeman <yturgema>
Component:	Backup-Restore.Engine	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	high	Docs Contact:
Priority:	high
Version:	future	CC:	bugs, lleistne, mtessun
Target Milestone:	ovirt-4.3.3	Keywords:	FutureFeature
Target Release:	---	Flags:	pm-rhel: ovirt-4.3+ mtessun: planning_ack+ sbonazzo: devel_ack+ lleistne: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.3.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-16 13:58:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yuval Turgeman 2018-08-08 11:44:16 UTC

Description of problem:
The engine-backup script takes a dump of the database and calculates its checksum with md5, which is not allowed in FIPS mode.

Comment 1 Sandro Bonazzola 2019-01-21 08:28:53 UTC

re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0.
If you think this bug should block 4.3.0 please re-target and set blocker flag.

Comment 2 Sandro Bonazzola 2019-02-18 07:55:02 UTC

Moving to 4.3.2 not being identified as blocker for 4.3.1.

Comment 3 Petr Matyáš 2019-04-05 11:26:24 UTC

Verified on ovirt-engine-4.3.3.2-0.1.el7.noarch

Comment 4 Sandro Bonazzola 2019-04-16 13:58:36 UTC

This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.