Bug 1613833 - [RFE] - Use SHA256 for engine-backup
Summary: [RFE] - Use SHA256 for engine-backup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backup-Restore.Engine
Version: future
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.3.3
: ---
Assignee: Yedidyah Bar David
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-08 11:44 UTC by Yuval Turgeman
Modified: 2019-04-16 13:58 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.3.3.2
Clone Of:
Environment:
Last Closed: 2019-04-16 13:58:36 UTC
oVirt Team: Integration
Embargoed:
pm-rhel: ovirt-4.3+
mtessun: planning_ack+
sbonazzo: devel_ack+
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 98658 0 master MERGED packaging: engine-backup: Use sha256sum for verification 2019-03-27 06:51:47 UTC
oVirt gerrit 98935 0 ovirt-engine-4.3 MERGED packaging: engine-backup: Use sha256sum for verification 2019-03-27 08:34:36 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.