Bug 1373183 – Add FIPS XTS key verification (encryption and tweak key must be different)

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

Bug 1373183 - Add FIPS XTS key verification (encryption and tweak key must be different)

Summary:	Add FIPS XTS key verification (encryption and tweak key must be different)

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	high Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Tomas Mraz
QA Contact:	Stefan Dordevic
Docs Contact:	Mark Flitter

URL:
Whiteboard:
Keywords:

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

Reported:	2016-09-05 08:40 EDT by Tomas Mraz
Modified:	2017-08-01 14:16 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	openssl-1.0.2k-1.el7
Doc Type:	Enhancement
Doc Text:	Ensure that AES-XTS support is compliant The current guidance for FIPS 140-2 validation has added the requirement to check whether both parts of the XTS key are different. This has been implemented.
Story Points:	---
Clone Of:
Clones:	1432994 (view as bug list)
Environment:
Last Closed:	2017-08-01 14:16:10 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:1929	normal	SHIPPED_LIVE	openssl bug fix and enhancement update	2017-08-01 14:08:01 EDT

Groups: None (edit)

Description Tomas Mraz 2016-09-05 08:40:48 EDT

Current implementation guidance for FIPS 140-2 validation adds requirement to check whether both parts of the XTS key are different.

We must implement this to make AES-XTS support compliant.

Comment 6 errata-xmlrpc 2017-08-01 14:16:10 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:1929

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