Bug 1108029 – Fipscheck does not report hmac checksum mismatch if the .hmac file is empty

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1108029 - Fipscheck does not report hmac checksum mismatch if the .hmac file is empty

Summary:	Fipscheck does not report hmac checksum mismatch if the .hmac file is empty

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	fipscheck (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Tomas Mraz
QA Contact:	Ondrej Moriš
Docs Contact:

URL:
Whiteboard:
Keywords:	FastFix

Depends On:
Blocks:	1367490 1425106
	Show dependency tree / graph

Reported:	2014-06-11 06:35 EDT by Tomas Mraz
Modified:	2017-08-01 12:46 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	fipscheck-1.4.1-6.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Clones:	1425106 (view as bug list)
Environment:
Last Closed:	2017-08-01 12:46:53 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:1971	normal	SHIPPED_LIVE	fipscheck bug fix update	2017-08-01 13:57:16 EDT

Groups: None (edit)

Description Tomas Mraz 2014-06-11 06:35:09 EDT

When the .hmac file is empty fipscheck does not report the checksum mismatch although it should fail the checksum test.

Comment 7 errata-xmlrpc 2017-08-01 12:46:53 EDT

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:1971

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